Organizations and members
An organization is Inklate's workspace — one per brand or client. Members hold a role, you switch orgs from the sidebar, and inviting teammates is a paid feature.
An organization is the workspace everything in Inklate lives inside — one per brand or client. Members belong to it with a role that decides what they can do, you switch between organizations from the sidebar, and inviting teammates is a paid feature.
The organization is the workspace
Everything you connect, create, and configure is scoped to one organization: channels, posts, labels, approval and publishing rules, analytics, API keys, and billing. Nothing crosses between organizations, so running one per brand or client keeps their data, teammates, and plan fully separate.
Your first organization is created during onboarding. Plans belong to the organization, not to you — every member of a subscribed organization shares its features, and if you belong to several, each carries its own plan. See Billing for how seats and plans work.
Switching and creating organizations
The organization switcher sits in the sidebar header, showing the active organization’s name and initial. Open it to:
- Switch — pick any organization you belong to. Inklate reloads so every scoped view (channels, posts, your role, analytics) re-fetches against the one you chose.
- Create — name a new organization inline; you land inside it once it’s created. A URL handle is generated from the name.
The switcher is always present, even with a single organization, so creating another is always one click away.
Members and roles
Each member holds one of three roles in an organization. Roles are enforced on the server for every action, and the interface only offers what your role can actually finish.
| Role | What it can do |
|---|---|
| Owner | Full control of the organization, including organization-level administration on top of everything an admin can do. |
| Admin | Connect and manage channels, manage billing, set approval and publishing rules, and manage API keys — plus everything a member can do. |
| Member | Create, edit, schedule, and publish posts; manage labels; read analytics; and decide on approvals they’re named in. |
The practical split: members run the content pipeline, while owners and admins hold the account-level controls — channel connections, billing, the API keys agents authenticate with, and the org-wide approval and publishing rules. A member never hits a dead end mid-action, because affordances they can’t complete aren’t offered in the first place.
Inviting teammates
Adding teammates to an organization is a paid feature. A free organization works solo — the single owner is its only seat. Once the organization is on a paid plan, you can bring in teammates, and each added member counts as another seat in the plan’s per-seat pricing.
When you try to invite from a free organization, Inklate points you to upgrade that organization rather than blocking you elsewhere in the app.
Publishing
When a post's moment arrives, each channel publishes independently — one failing never blocks the others — with automatic retries, honest partial-failure results, and a read-only status view.
Approvals
Turn on an approval lane so a post needs teammate sign-off before it publishes. Reviewers work a queue, rules set who and how many, and editing an approved post resets it.