Teams

A team is the top level of Nekomind's access model. It groups people, owns workspaces and projects, and gives everyone in it a role that applies to everything the team owns.

What a team is

A team is a named group of people with a role each. It is the level above workspaces: a workspace or project can be owned by a team, and every member of that team inherits access to it without being invited to each one separately. Teams are also where a shared subscription lives, which is why the team owner is the only person who can reach billing.

You do not need a team to use Nekomind. A personal account owns its own workspaces directly. Create a team when more than one person needs standing access to the same work.

Creating a team

  1. Open Teams from the main menu.
  2. Choose Create new team and give it a name. The name is what colleagues see in invitations and next to shared projects.
  3. You become the team's Owner. A team always has at least one Owner.
  4. Open the team and add the workspaces it should own, or create new ones inside it.

Inviting people

Open the team, choose Invite, enter the person's email address and pick the role they should hold in the team. They receive an invitation they can accept or decline; until they accept, the invitation sits in the team's pending list and you can cancel it.

  • An invitation names one team and one role.
  • An invitation expires. If it lapses, send another one.
  • The person sees pending invitations under Invites, and accepting one adds them to the team immediately.

Roles inside a team

Every member holds one role in the team. Owner has unrestricted control including billing and deletion. Admin can invite people and manage members and settings, but not billing. Editor and Member can work inside the team's content, Editor with broader edit rights. Commenter can read and comment. Viewer can read. Guest is scoped to a single resource rather than the team as a whole.

The full capability matrix — what each role may read, comment on, edit, invite and delete — is on the roles page. /docs/roles

How a team reaches a workspace and a project

Access resolves from the most specific grant to the least. A role granted directly on a project wins over one granted on the workspace, which wins over the role someone holds in the team. So team membership is the baseline: it gives everyone standing access to everything the team owns, and any workspace or project can raise or lower one person's role above that baseline.

A Member of the team can be the Owner of one project inside it. If no grant exists at any of the three levels, access is denied.

A team is not the same as a direct invite

  • A team invitation adds a person to the group. Their role applies to every workspace and project the team owns, including ones created later, and it is removed everywhere at once when they leave the team.
  • A direct invite to a workspace or project grants one person one role on that one resource. Nothing else follows from it, and it does not appear or disappear when a team changes.

Use a team for colleagues who will work across the shared body of work. Use a direct invite for a client, a contractor or an agent that should see one project and nothing more.