Use this guide alongside the current product documentation. Available models, integrations and allowances depend on your configured account.
Set up an organisation and invite the right people
Open Organisation in the sidebar, enter its name and estimated team size, and add optional context about your work. The estimate describes the team; it does not increase the plan's seats. The creator becomes the owner and can invite members or administrators by email.
An invitation is bound to one recipient. The recipient signs in to the matching account and explicitly accepts the link. Pending invitations reserve seats, including when the recipient has not joined yet. An owner or administrator can revoke an unused invitation.
| Role | Responsibility |
|---|---|
| Owner | Manage the organisation, administrators and membership. |
| Admin | Invite and manage members; manage shared work. |
| Member | Work on shared workflows when collaboration is enabled. |
Choose which workflows become shared
Existing personal workflows remain private. Their creator can explicitly share a saved workflow with the organisation from the builder. New workflows created in the organisation belong to it. Shared work stays with the organisation when a member leaves.
A person's connected accounts and personal AI keys retain their credential ownership. Membership is not a transfer of those secrets. Workflows that rely on a departed creator's connections may need an active member to duplicate them and reconnect the required accounts before they can run.
What happens when two people edit at once?
Superagento tracks saved workflow revisions and checks for updates while the editor is open. Independent changes can be merged. If both people change the same value, the editor stops automatic saving and keeps the local work available to export or compare with the latest version.
This collaboration uses polling and conflict-aware saves. It is not character-by-character live cursor editing. Agree on who is changing connected credentials or action destinations when testing a shared workflow, and review the saved graph before activating it.
Understand shared seats, workflows and credits
An organisation uses its assigned plan and any administrator-configured exceptions. The current Organisation and Plans & usage screens are the source for its allowances. Site-wide plan defaults can change without a code release, while an organisation may have custom limits.
Seats include the owner and outstanding invitations. Reaching a cap blocks the relevant new work; lowering a cap does not remove existing members or delete workflows. Check shared usage before scheduling a large batch, and remember that personal account allowances remain separate from the organisation.
Frequently asked questions
Can I invite someone who already has a Superagento account?
Yes. They use the invitation link, sign in with the invited email and explicitly accept. A person can belong to one organisation at a time.
Does sharing a workflow share my API key?
No. Keys and connected accounts retain their ownership. Shared workflow access does not expose personal provider secrets.
Can two teammates save changes at the same time?
Yes. Saves use revision checks. Independent edits can merge; overlapping changes produce a conflict that must be reviewed.
Does changing team size unlock more seats?
No. The team-size estimate is descriptive. The assigned plan and administrator settings determine the actual seat allowance.
Put the idea into practice
Start with a small test and a result you can verify. Keep the first destination reversible, then inspect the complete run before turning on automatic actions.
Related guides
- AI Workflow Automation for Small Teams
- Visual AI Agent Builder for Your Team
- Google Sheets AI Automation: Read, Process and Write