Board Team Management
Invite, manage roles, and remove board members in Syndic+.
Two role levels#
Syndic+ distinguishes two role levels:
| Level | Examples | Scope |
|---|---|---|
| Application | admin, user | Global platform access (super-admin) |
| Organization (syndicate) | owner, admin, member | Access to syndicate resources |
Board "business" roles (chair, secretary, treasurer) are stored as metadata. They are informational — they don't grant different technical permissions.
Organization roles#
| Role | Capabilities |
|---|---|
owner | Everything — including delete syndicate, change plan, invite other owners |
admin | Full CRUD on data, invite members and admins |
member | Read + limited write depending on module |
Access team management#
Settings → Team (/dashboard/settings/team) — reserved for owners and admins.
Invite a member#
Click 'Invite'
Invite member button in the top right.
Fill in details
- Email (required)
- First name, last name (optional — asked at signup)
- Organization role (owner, admin, member)
- Board role (chair, secretary, treasurer, director)
Send the invitation
Click Send. The invitee receives an email with a unique link valid 7 days.
Follow-up
The invitation appears as pending. You can resend or revoke it if needed.
Board roles#
Business roles are added to the record to mirror how the board is organized:
| Role | Typical responsibilities |
|---|---|
| Chair | Presides meetings and board sessions, signs resolutions |
| Vice-chair | Replaces the chair in absence |
| Secretary | Drafts minutes, manages official correspondence, maintains syndicate book |
| Treasurer | Tracks accounting, presents financial statements at the AGM |
| Director | Sits on the board without a specific role |
These roles appear on official documents (minutes, certificates) and help assign actions.
Edit or remove a member#
Click a member's context menu (···):
- Change role — promote or demote (owner ↔ admin ↔ member)
- Change board role — update the business role
- Transfer ownership — if you're an owner and want to hand off to another member
- Remove — the member immediately loses access to the syndicate
A syndicate must always have at least one owner. You cannot remove yourself if you are the sole owner — transfer first.
Best practices#
- Least privilege: give the most restrictive sufficient role
- Multiple owners: keep at least 2 owners to avoid lockouts (departure, forgotten password)
- Election refresh: after the AGM election, update board roles
- Deactivation vs. deletion: prefer removing access over deleting the historical record
- Audit: all team actions are logged (Bill 25 — duty of diligence)
Managing via MCP#
Members can be managed programmatically via the MCP API. See API Reference — Co-owners and MCP Server.