Teams & access
Company and project roles, seats, invitations, teams, and giving people or whole teams access to each project with Members & access in BoardMark.
Which roles are there?
| Scope | Role | Can |
|---|---|---|
| Company | Company admin | Users, seats, invitations, teams, permissions, billing, tax profile, creating and deleting projects, closing billing to delete the company — always a project admin everywhere |
| Company | Company member | Sees only projects they were given access to |
| Project | Project admin | Project settings, environments, parallel sprints, members & access, managing sprints, deleting or restoring the project |
| Project | Member | Create, edit, move and assign issues, comment and attach files |
| Project | Viewer | Sees the board and issues but cannot change anything |
How do seats work?
- Enabled — can open the board and counts as a seat
- Suspended — no access, not billed; can be enabled again
- Deactivated — no longer used, not billed
- AI agents are never seats
How do I give access to a project?
Open Project settings → Members & access (or the admin console's Project members tab), search for a person or pick a team, and give Project admin, Member or Viewer. Change roles or remove access in the same list.
- A team grant covers everyone in the team, now and later
- Each person's effective role is the highest of their own and every team they are in; the list shows which team it comes from
- Company admins are always project admins
- The last project admin cannot be demoted or removed
- Everyone else sees the list read-only
- The people you add (directly or as a team) get an email, a bell entry and a LINE card (Premium) saying who gave them access, and see the project in their list at once; they can turn it off in Settings → Notifications (Added to a project). A role change or a removal notifies nobody
The list starts with what each role can do in plain words. In the admin console, the ⓘ next to a member shows their teams and the projects they are in with the role (given directly or through a team), and a team's ⓘ shows the projects the team is assigned to.
Can I open a project to the whole company?
Yes. In Project settings → Members & access → Company-wide access choose Off (default), Everyone in the company as member, or Everyone as viewer. You can also choose it when you create the project.
- A role set directly or through a team always wins, higher or lower: someone set as viewer stays viewer even when company access is member
- Company admins remain project admins
- People who get in only through company-wide access never manage releases
- Turning it on notifies nobody, and every change is in the company audit log
- Turning it off removes everyone without a direct or team role at once
- Seats are unchanged (counted per company)
- The project then shows in everyone's dashboard, people pickers and list_projects, and list_people marks such people via: "company"
What are teams for?
Company admins create teams in the admin console; a person can be in several teams. Give a project to a team once instead of person by person. Individual accounts have one member, so they have no teams.
Can I see who did what in the company?
Yes. Company admins open the Audit log page in the admin console to see the company's key events: sign-ins (successful and failed), tokens and AI agent connections, members, roles and teams, project creation and settings, billing, Jira imports, deleted issues, docs or comments, and AI agent requests BoardMark refused — no permission, or a rule such as “agents change statuses on a Scrum board only in a sprint a person started” — shown as “An AI agent was refused”. Click a row to see the before and after.
- Filter by date, category, person or how it was done — in the web app, through an AI agent, automatic (system) or BoardMark staff
- Export to CSV or JSON with the same filters, up to 1 year per export — JSON is meant for security (SIEM) and archive tools
- Kept for 1 year
- Edits to issues, comments and docs are in each item's own history instead
Can I see what an AI agent did?
Yes. Every change an AI agent makes through BoardMark's MCP server is recorded in the issue or doc history with:
- Whose rights it used
- Which AI client — for example Claude Code: the name the person approved when connecting with sign-in (OAuth), or the name they gave a personal access token
- Whether it connected with OAuth or a personal access token
- Which MCP tool made the call, for example update_issue
- A request id tying together everything one call changed
Issue history shows these changes as “via Claude Code” (the client's name, plus its role if set — “via Claude Code · QA”). Company admins can filter the Audit log to what was done through an AI agent, including the requests BoardMark refused.
Premium companies can give an AI agent its own account (an agent account) with an owner, a run log and an instant pause — see the “Agent accounts” docs page.
The AI decides nothing on its own authority: an agent has only its user's own rights (user parity), and agent tokens never get admin, billing or permission tools.