Invite teammates and manage workspace roles
Bring people into the right organization and give them access suited to their work.
On this page
Choose the organization before inviting anyone
Each organization holds its own inboxes, contacts, campaigns and members. Select the organization the teammate should work in before opening Settings. Decide whether the person needs to manage campaigns, handle replies or perform another defined task. Roles control what members can view and change. The public guides explain how to assign and review roles, but do not provide a complete list of role names or permissions.
Use the teammate’s intended work email for the invitation and tell them which organization to expect. If they already belong to another organization, they can use the organization switcher after joining; they do not need a duplicate workspace just because they work on several projects.
Invite and assign the role
Open team settings
Go to Settings and find the team or members section for your organization.
Expected result: The team or members section belongs to the intended organization.
Send an invite
Enter your teammate's email address and send the invitation to join your organization.
Expected result: The invitation is addressed to the correct teammate.
Assign a role
Choose a role for the new member. Roles control what they can see and do, so pick one that matches their responsibilities.
Expected result: The selected role matches the responsibilities you intend to grant.
They accept and join
Your teammate receives the invite by email and accepts it to join your workspace. From there they can start working alongside you.
Expected result: The teammate accepts the email invitation and can enter the workspace.
Test access against the person’s job
| Item | How to use it |
|---|---|
| Campaign preparation | Confirm the member can reach the intended campaign work and the correct audience. |
| Reply handling | Confirm the member can access the relevant conversations and follow the team’s ownership process. |
| Administration | Grant administrative capability only where the role and task require it. |
| Several projects | Check each organization separately; membership in one is not evidence of membership in another. |
Example teammate handoff
Organization: the project you have been invited to
Your work: review replies and answer service questions
First task: open the agreed pilot conversation in Inbox
Escalation: refer pricing or unusual commitments to the project owner
Campaign changes: follow the team’s agreed ownership processThis is an internal handoff example. It does not define software permissions or promise that the available role names match these job descriptions. Select from the actual roles in the member settings, then have the teammate confirm that the needed task is accessible. If an operation is missing, investigate the role and workspace instead of sharing another person’s login.
Review roles when responsibilities change
Return to the team settings to review or update a member’s role. Check the person’s current responsibilities, not only the role assigned when they joined. A teammate who moves from campaign setup to reply handling may need different access. For work across organizations, repeat the review in each relevant workspace. Keep a simple record of the intended responsibility so later administrators understand why the role was chosen.
Resolve a missing invitation or feature
Ask the teammate to check the invited mailbox and spam folder and confirm which account they used to sign in. Then check the organization switcher and the invitation or member entry. If the workspace is visible but a feature is missing, compare the assigned role with the available permissions. The guides do not specify invitation expiry or every role capability, so use the actual status and ask DigLab about any unresolved mismatch.