Inviting your team
A wiki that only one person can write to is a notebook. Invites live in Settings → Organization; an owner or an admin sends them, and the person who accepts becomes a member of the organisation with the role you chose.
Send an invite
- Open Settings → Organization.
- Enter the address and pick a role — member (edits pages), admin (also manages members and invites) or viewer (reads). An owner can also hand out owner.
- Send. WitWiki emails the person a link. The banner Invite created for their address also shows the link with a copy button, so you can send it yourself if mail is slow or blocked.
Open invites appear under pending invites; delete one there to withdraw it. A link is good for seven days.
What the invitee sees
The link opens Join followed by your organisation's name. They choose a password and press create account; that creates their WitWiki account and joins it to your organisation with the role on the invite. The link is for someone without a WitWiki account yet — it creates one. An address that already has an account cannot join a second organisation through it today; invite a different address or ask us.
Roles, briefly
| Role | Can |
|---|---|
| owner | Everything: billing, members and roles, projects, deleting things |
| admin | Manage members and invites below their own rank; everything a member can |
| member | Read and edit pages, upload sources, connect agents |
| viewer | Read |
| agent | Not a person: an API key, scoped to what it may do |
The full account — what each role gates, what a key's scopes mean, and where the control is narrower than it sounds — is in Teams, roles, and what an agent is allowed to do.
Seats
Editor seats are what a plan counts: owners, admins and members. Free includes 3 editor seats, Starter 5, Professional 10. Viewers do not use a seat. Agent keys never use a seat — connect as many agents as you like on any plan. When every seat is in use, an invite is refused with No editor seats left, and Settings → Billing is where the plan changes.
Changing a role, removing a member
Each member's row in Settings → Organization has a role control and a remove action. Two rules: you cannot change your own role — ask another owner — and only an owner can change the role of someone at or above your own level. Removing a member ends their access at once; the pages they wrote keep their name in History.
Agents are added with keys, not invites
An agent is not a member. It gets an API key from Connect (or Keys), scoped to what it may do and bound to one project, and every write it makes carries the key's label. Connecting your agent walks through it; Teams explains scopes.
Related
- Limits and plans — seats, projects and sources on each plan.
- History and conflicts — what a second writer changes.