Team & roles

Everything in cadence. belongs to one team workspace. This page covers who is in it and what they can do.

Inviting people#

Admins invite by email from Team in the account menu. The invitee gets an email; following the link puts them in your workspace with immediate access to its projects, templates and tags.

Invites count against your plan's member limit — five on the free plan, unlimited on Pro and Enterprise. See plans and limits.

Admins and users#

There are two system roles.

Adminsystem role

Can invite and manage members, manage the team's plan, create and revoke API keys, and add or remove AI agents. Admins can do everything a user can.

Usersystem role

Full access to the work: create and edit projects, phases, tasks, criteria, templates and tags; comment; be assigned work. Cannot manage members, billing, keys or agents.

The split is intentionally coarse. cadence. does not have per-project permissions — anyone in the workspace can see any project in it. If you need work invisible to the rest of the team, it needs its own workspace.

Job title and department#

Separate from the system role, each person has a job title — "Regulatory Affairs Manager", "Formulation Scientist" — and a department. These are descriptive, not permissions: they make assignee pickers and the team directory legible when the workspace grows past the point where everyone knows everyone.

Skills#

Skills are the part of a profile that actually changes behaviour.

A person's skills are matched against the skills a task requires when a project allocates its unassigned work automatically. Without skills on both sides, allocation has nothing to go on and simply spreads work evenly.

Two habits make it worth doing:

1. Keep the vocabulary small and shared. Regulatory beats regulatory affairs, Reg, and EU Reg coexisting.
2. Record skills in your templates, so every project inherits them from the start.

Agents in the team#

Pro

Connected agents get a profile in your team and appear alongside people in assignee lists and the directory, marked as agents. An admin adds and removes them. Assigning work to one queues a run against its MCP endpoint — see AI agents.

Removing people#

Admins can remove members. Their completed work, comments and history stay — removing a person does not rewrite the record.

Your own profile#

Profile in the account menu is where you set your own name, avatar, job title, department and skills, and change your password. See profile and preferences.