MarssteinDocs

Core

Teams and members

How teams, members and access scopes work in an organisation.

Organisation and teams

An organisation is your company workspace. Inside it you create teams, for example for a client, a project or a department. In the code a team is called a project, and the app shows it as Team. Every organisation has a Default team (shown as Default) whose name cannot be changed.

In short

Pages at the base level cover the whole organisation. Pages inside a team show only that team's documents, tasks, risks and sessions. Data is always separated per organisation.

Try it

Open the team switcher at the top of the sidebar and press Create Team.

Enter the Team Name (required) and, if useful, a description.

Save. Pick the team in the switcher to work inside it.

Good to know

  • A team name must be unique in the organisation.
  • Deleting a team asks you to type the confirmation text; the team's data goes with it.

Members

Under Settings, Auth, Members & Invites you see the Members of the organisation with their role, when they joined and where their access applies (Organization-wide, All teams or the named teams).

In short

A member has one role and one or more seats. An organisation-wide seat applies in every team. A team seat applies only inside that team and never raises an organisation-wide seat.

Try it

Open the Members & Invites tab and find a member.

Change the role from the member's row, or open Where applies to see the scope.

Use Remove to take a member out of the organisation or out of one team.

Good to know

  • Whoever holds only a team seat cannot read the audit log, invite people, change settings or create teams.
  • Roles and what each may do are described in Sign-in and roles.

Invitations to teams

An invitation can be organisation-wide or limited to chosen teams. You can invite several addresses at once and set role and team per address.

Try it

Press Invite, add addresses and choose Team-specific access.

Select the teams and send. Pending invitations stay in the list until they expire or are revoked.

Good to know

  • A person who asks to join appears as an access request in the member list. An administrator approves or denies it.

Per-team permissions

Rights can be tuned for a single member: the owner can check or uncheck individual rights, and Reset returns to the role defaults. Permissions preview shows the effective result.

In short

Use roles first, custom roles second and individual overrides last.

Good to know

  • Setting individual rights is reserved to the Owner.

On this page