Wolfix
Back to help center

Step-by-step · Account And Billing

Invite a teammate

Add someone to your workspace without handing over repo access.

Reviewed by OperationsUpdated May 28, 20263 min readSuggest edit

You'll need

An owner or admin seat on the workspace

Time

~3 min

Plan

Seats vary by plan — see /pricing

Most teams need to add someone before launch — a designer to action brand findings, a virtual assistant to file documents, or a co-founder who owns the legal blockers. Wolfix lets you invite that person into your workspace with their own login, and it keeps your code connection separate from workspace membership. A common founder worry is that adding a designer or VA will expose the GitHub repo. It won't: a teammate seat grants access to projects and reports, not to the connected source code, unless you deliberately grant it.

Open the team settings

From your dashboard, open Settings and select Team. This is where every member of your workspace is listed, along with their role and the date they joined. If you don't see a Team tab, you're on a seat that can't manage members — ask an owner or admin to send the invite.

Fig. 01Settings: the Team tab listing current members and roles · screenshot pending

Send the invite

Click Invite teammate and enter the person's email address. Choose a role for them — a member can open projects and reports and act on findings, while an admin can also manage billing and other members. Pick the lowest role that lets them do their job; you can change it later.

The person receives an email with a link to create their own Wolfix login. They never see your password, and their access is tied to their own account, so you can remove them cleanly whenever the work is done.

Fig. 02Invite form: email field and role selector · screenshot pending

A seat is workspace access, not code access

Inviting a teammate adds them to your workspace so they can see projects, reports, and generated documents. It does not give them access to a connected GitHub repository. Your code connection stays private to the people you explicitly grant it to.

Keep the GitHub connection private

This is the step that matters most when you're adding a designer or VA. A connected GitHub repository is owned at the project level by whoever connected it — the invite you just sent does not pass that connection along. Your teammate works from the report Wolfix already produced: findings, severity, generated documents, and brand assets. They never touch the repo, the access token, or the source.

If you later need a teammate to refresh or reconnect the code — say, a technical co-founder — you grant that separately, and only to them. The default is that everyone you invite is a report-and-documents collaborator, not a code collaborator.

Don't share your own GitHub login to grant access

If a teammate genuinely needs to reconnect the repo, have them connect it through their own GitHub account on the project's connect screen. Never share your GitHub password or personal access token to work around seat permissions — that exposes far more than Wolfix needs.

Confirm they joined

When the invite is accepted, the person moves from Pending to an active member in the Team list, with their role shown beside their name. Open the list to confirm the role is what you intended. To remove someone later — for example a contractor whose project is finished — use the menu beside their row; removing a member revokes their access immediately without affecting your projects or your code connection.

Fig. 03Team list: a teammate now active with their assigned role · screenshot pending

Share a single report instead of a seat

If someone only needs to see one report — a lawyer or an advisor — you may not need to add them at all. Export the report to PDF or copy a report link and skip the seat entirely.

You just did

Your teammate is in

  • Opened the Team tab in workspace settings
  • Sent an invite with the right role
  • Confirmed the invite never exposes your GitHub connection
  • Verified the teammate is active and can be removed cleanly later

Was this article helpful?

Related articles