Each member is assigned one of three predefined roles, which determine their level of access and scope of permissions within the team.
Role [2] and Permission Structure:
Owner: This is the role with the highest administrative privileges. The Owner has full control over the team, including the ability to permanently delete it. Their responsibilities also include member management: inviting new users, modifying their roles [3], and removing them from the team [5].
Editor: This role grants full permissions for managing projects and their associated assets. An Editor can create, modify, and delete projects but does not have access to team-level administrative functions, such as user management.
Viewer: This role provides read-only access to all projects and resources within the team, without any editing capabilities. It is designed for stakeholders who need to monitor project progress without directly intervening in the work.
Invitation Process
When an invitation is sent to a new team member, their status in the user list will appear as "Invited" [1] until they accept the invitation, which is delivered to the specified email address.
Example of e-mail invitation.
Users who have joined a team by invitation are permitted to leave it at any time. This functionality provides flexibility and autonomy in managing one's affiliation with various workspaces.
It is important to note, however, that this privilege does not extend to users with the "Owner" role. Due to their critical administrative responsibilities and accountability for the team's integrity, Owners are restricted from leaving a team they manage.