Approvals and team

Nothing is sent until a version is approved, except a handoff, which is never sent. The worker publishes the frozen copy. It does not approve.

Approve a post

1. An editor saves the version and chooses Submit for review.
2. An approver, owner, or admin opens the review screen.
3. Approving stores the payload that will be sent. Later edits of the source do not rewrite that payload, and they do not rewrite a published post.

If Team has “require a distinct approver” on, the person who submitted the draft cannot approve it. Someone else with the approver role has to accept it.

A failed post can be turned back into a draft and submitted again. An uncertain post is not submitted again. Look it up.

Roles

Role	Draft	Schedule	Approve	Connect and invite
Owner, admin	Yes	Yes	Yes	Yes
Approver	Yes	Yes	Yes	No
Editor	Yes	Yes	No	No
Scheduler	No	Yes	No	No
Viewer	No	No	No	No

An invitation can be for the workspace, one brand, or one account. The server checks that scope on every action.

Invite someone

On Team, owners and admins enter an email and a role, then choose the scope.

The invitation is recorded. No email is sent. Email delivery is coming soon. The page shows a link. Copy that link to the person through a channel you already trust. The link expires. Accepting it requires the person to sign in. The address on the invitation has to match the user who accepts it.

The Team page also lists members, open invitations, and recent audit events. The audit records who did what. It does not store tokens.

Assistants and approval

An AI client cannot approve while the approval policy on Settings is “Never”. That is the default. See AI features. A person still approves.