Manage team members
Invite people into the organization, see who already has access, and remove access when someone leaves. Run this whenever the team changes.
Goal
An accurate list of who can read the portfolio and operate on it, with no stale invitations left open.
Steps
Open settings and read the current members
The members list shows everyone in the organization and the role each one holds. Membership is organization-scoped, which is the same boundary that scopes the portfolio, the evidence, and the decision ledger.
Invite by email
An invitation records the email address, the role you are granting, who sent it, and when it expires. It starts in a pending state and stays that way until the person accepts.
Check pending invitations
Pending invitations are listed separately from members, because an invitation is not access. Someone who has not accepted cannot read anything. Invitations expire, so an old pending entry usually means it needs sending again rather than waiting on.
Confirm the new member appears
Once accepted, the person becomes a member of the organization and appears in the members list with their role. From that point they read the same portfolio and decision ledger you do.
Remove access when someone leaves
Removing a member ends their access to the organization. Nothing they recorded is removed: evidence and decisions stay in place, because the ledger is a company record rather than a personal one.
Worth knowing
People and agents are separate grants
Adding a person does not authorize their agent, and authorizing an agent does not add a person. Connect an AI agent covers the other half.
Removing a member does not rewrite history
Decisions are immutable and stay attributed as recorded. If a call made by someone who has left is wrong, supersede it rather than trying to remove it.