Invite your team

You will learn how to add teammates without giving too much access too early.

Tixio has two access layers to think about:

Workspace access lets someone enter the workspace.
Project access controls which private projects they can see and work in.

Team-visible projects are available to workspace members. Private projects need more deliberate project membership.

Decide who to invite first

Invite a small setup group before the whole team. A good first wave is:

One workspace owner or admin who can help manage access.
Project leads who understand which work belongs in each project.
A few teammates who can create real issues and give feedback on the setup.

After that group confirms the workspace and project structure, invite everyone else.

Invite workspace members

Open the workspace, then go to Settings > Members.

If your role can invite people, select Invite member and enter:

The teammate's email address.
The workspace role they should have.

Use Member for most people. Use Admin only for people who need to manage workspace settings, members, integrations, or other administrative surfaces. Keep owner access limited to the people responsible for the workspace.

The member list shows pending invitations, joined members, roles, and actions available to your role.

Invite with the exact email address

If your teammate already has a Tixio account, invite the email address they use to sign in. This avoids confusion when they accept the invitation.

Understand workspace roles

Workspace roles are about administration, not day-to-day issue ownership.

Owner controls the workspace and should be rare.
Admin helps manage workspace settings, members, and integrations.
Member does normal project and issue work.

Some controls are hidden unless your role can use them. For example, only people with the right workspace role can invite members or change certain settings.

Give project access

After someone has workspace access, check whether they can see the projects they need.

For Team projects, workspace members can access the project without a separate project invite.

For Private projects, open the project and use the Members tab to add the people who should work there.

Use private projects when the work is sensitive, experimental, customer-specific, or limited to a smaller group. Use team-visible projects for shared work where the whole workspace benefits from visibility.

Help invitees get oriented

Send new teammates a short message with:

The workspace name they should choose.
The first project they should open.
The first saved view, board, or backlog they should check.
Whether they should create issues, comment on existing work, or only review.
A link to Five-minute tour.

Example:

Welcome to Tixio. Open the Acme workspace, then open the Product project.
Start with the Backlog tab and add any missing launch tasks as issues. If you
are not sure where something belongs, create it with the label "needs triage".

Keep access tidy

Review membership when teams change. Remove people who no longer need access, cancel stale pending invitations, and keep admin roles limited.

Before making a project private or removing someone from a project, check whether they own active issues, saved views, dashboards, or automation rules that other teammates rely on.

Troubleshooting

If someone cannot accept an invitation, ask them to sign in with the invited email address, confirm their account if prompted, and reopen the invitation link.

If someone can enter the workspace but not a project, check the project visibility. Add them to the project if it is private, or consider whether the project should be team-visible.

If the Invite member button is missing, your role may not allow invitations. Ask a workspace owner or admin to invite the teammate or update your role.