Team

The Team section is all about collaborating on content: invite colleagues and agency clients, assign roles, set a shared post language, and configure approval chains so that no post goes live without a review.

Teams and personal space

Every user has a personal space, and on top of that you can create separate teams (organizations) — for example, one per agency client. You switch between them in the header of the Team section: pills with the team name and your role in it, and the ”+ New team” button creates another one.

Note

You can only invite members into a team. The invitation form is unavailable in your personal space — create a team first.

How to invite a member

1. Open the Team section and select the team you need.
2. In the “Invite member” card, enter an email, choose a role, and click “Send”.
3. Until the person accepts the invitation, they’re shown in the member list with an “Invitation sent” label.

Only the Owner and Admin can invite. A member’s role can be changed later — via the menu in the member’s row (that’s also where “Remove from team” lives).

Seat limit

The number of seats in a team depends on your plan — the “N / M seats” counter is visible in the section header and gets highlighted when you’re running out of seats. Current limits are in the Plan section in the app.

Roles and permissions

There are four roles in a team. In short: the Owner can do everything, the Admin manages everything except deleting the team, the Editor works with content, and the Viewer can only look.

Permission	Owner	Admin	Editor	Viewer
Viewing content and sections	✓	✓	✓	✓
Creating and editing content	✓	✓	✓	—
Inviting members and changing roles	✓	✓	—	—
Approving posts (without a chain)	✓	✓	—	—
Configuring the approval chain	✓	✓	—	—
Brand content language	✓	✓	—	—
Deleting the team	✓	—	—	—

There’s also a role hint with descriptions right in the app — the “Roles and permissions” card at the bottom of the section.

Brand content language

The Team section has a “Brand content language” card — this is the default language in which the AI writes posts for the whole team. It’s handy when the brand’s audience speaks a different language than the interface: everyone has their own interface language, but posts come out in the brand’s language.

• The “Auto” value means the AI follows the language of your brief.
• For an individual post you can override the language in the composer — the “Post language” picker (see Content plan).

Only the Owner and Admin can change this setting.

Content approval

An approval chain is a sequence of review stages a post passes through before publication. Each stage has its own reviewers: team members and/or clients via Client Review links. Available on all plans.

How to set up a chain

1. Open the Team section and follow the approval settings link in the header.
2. Add stages with the “Add stage” button: each one has a name, reviewers, and a decision mode.
3. Enable the chain and save. Each stage must have at least one reviewer — otherwise you won’t be able to save.

Decision mode for a stage:

Mode	How it works
Any	Approval from a single reviewer of the stage is enough — the post moves on
All	The post moves to the next stage only after every reviewer approves

There’s one chain per team — it applies to all posts submitted for approval.

How a post moves through stages

1. The post is submitted for approval and lands on the first stage. Reviewers of this stage get a notification in the app; clients see the post on their approval page via the link.
2. In the Content plan, the post gets an “Approval stage” block with the chain of stages: completed ones are green, the current one is blue, and future ones are gray.
3. If you’re a reviewer of the current stage, you have the Approve, Request changes, and Reject buttons plus a comment field. Everyone else sees the “Waiting for this stage’s reviewers to decide” label.
4. Once the last stage is approved, the post is considered approved: a scheduled one goes into the publishing schedule.

The full history of decisions with comments is saved — expand the “History” block under the chain in the post card.

Rejection and edits

• Reject — give a reason, the post gets the “Rejected” status and isn’t published.
• Request changes — the post returns to drafts along with the comment; the author reworks the text and submits it for approval again.

Tip

A client using a Client Review link simply clicks “Approve” on their page — the system figures out which stage of the chain the post is at on its own. If the client is assigned as a reviewer of a later stage, the action becomes available once the post reaches their stage. Learn more in the Client approval section.

If a chain isn’t configured

Without a chain, simple approval works: all Admins and the Owner get a notification, and any of them approves or rejects the post directly in the Content plan. On top of that, an Admin can always approve a post bypassing the chain — for cases when publication is urgent and reviewers are unavailable.