Team access becomes confusing when a project link is treated like membership or when every collaborator receives administrative power. In voiqq, a workspace has one protected Team leader, optional Team admins, and Workspace members. Public project links use a separate permission system. Choose the smallest role that lets each person complete the work they were invited to do.
Choose the right workspace role
- Team leader owns the workspace, controls member roles, and must transfer ownership before leaving or deleting the account.
- Team admin can manage projects and routine team work, but cannot replace or remove the Team leader.
- Workspace member can work in projects made available through project membership, assignment, or the workspace permission rules. This role does not grant workspace administration.
- A person opening an enabled project share link is not a team member. Their access remains limited to the project and to its current View only, Commenter, or Editor setting.
Invite a colleague
- Open the workspace and choose Team from the main navigation.
- Find the Invite people section and enter the colleague's email address.
- Open Workspace role and choose Team admin or Workspace member.
- Choose Send Invites. voiqq emails a protected invitation to the address you entered.
- Ask the recipient to sign in with that same email address and accept the invitation.
- Return to Team and confirm that the invitation moved from the pending list to the active member list.
Change a role or remove access
The Team leader can change an active member between Team admin and Workspace member from the Team page. Use Remove only when access should end. Removing a member clears their project membership and active finding assignments according to the existing cleanup rules. voiqq blocks any action that would remove the protected Team leader or leave the workspace without an owner.
Give access to a project
Workspace membership and project access answer different questions. Membership identifies who belongs to the team. Project membership and finding assignment determine which work a Workspace member can use. Open the project, use its member or assignment controls, and confirm the intended person can see only the project work they need.
Use public sharing deliberately
Open Share inside a project. Private keeps the project out of public routes. Anyone with link creates a protected share route and enables View only, Commenter, or Editor. These labels describe public-link access; they do not create a team account and do not grant workspace administration. Return the project to Private when external access is no longer required.
Check the result
- One active Team leader remains recorded for the workspace.
- Every Team admin genuinely needs administrative access.
- Workspace members can reach the projects or assigned findings required for their work.
- Pending invitations use the intended address and role.
- Public share settings match the external access you meant to provide.
- Former collaborators no longer appear as members or assignees.