Workspace & Projects#

The workspace is your global workspace. It contains all of your projects (brands), each isolated with its own brand identity, social channels, and analytics.

Project Structure#
01

Workspace

One workspace per user account. Contains all your projects. Linked to a pricing plan.

02

Project

Represents a brand or client. Each project has its own brand identity, social accounts, content, library, settings and automations.

03

Active Project

Only one project is active at a time. The project switcher (logo top-left of the app) allows you to toggle between projects. The active project defines the context for all operations.

SectionRoleConfiguration
VibeConversational AI brain: chat, generate, publish, ask anythingNone
StudioFlyer and video generationBrand identity required
OperationsAn operation gathers what Studio and VIBE produce, what Posts and Campaigns distribute, and what the Inbox receivesNone
LibraryAll generated & uploaded media in one place, paginated (“Load more”); a “Studio / Montages” filter isolates videos exported from the montage. A media's info sheet links to its Node Canvas composition, VIBE conversation or originating automationAutomatic
AgentsSpecialized marketing agents and website integration; configuration is reserved for the Owner and AdminsSelected project
InboxIncoming comments + auto-reply. Comment replies on Instagram, Facebook, and LinkedIn; DMs on Instagram and Facebook only (LinkedIn has no public API for DMs), TikTok has no public reply.Webhook + OAuth
PostsThree tabs: Posts (drafts and published), Schedule (publish queue and calendar), AnalyticsSocial accounts required to publish
AutomationsRecurring workflows (Monday morning, etc.)Manual configuration
CampaignsAd campaigns (Meta, Google, TikTok, LinkedIn), email and SMS, with their Analytics tabProvider configured
MarketplaceSubscriptions, credit packs, extra seats and account optionsNone
API KeysREST keys and MCP connections to control Gliiz from your tools; website integrations are configured in AgentsREST: plan-dependent; MCP OAuth: all plans
SettingsProject settings: brand, social accounts and team. Account billing and security are in WorkspacesDepends on role and scopes
BYOS Google Drive (Bring Your Own Storage)#

For agencies and enterprises (Agency and Enterprise plans), Gliiz offers BYOS (Bring Your Own Storage) via Google Drive. By connecting your Google Drive account in Project Settings (Accounts tab), all generated assets, flyers, images, and videos, are automatically copied in the background to a dedicated folder named 'Gliiz AI - [Project Name]' in your cloud.

External storage does not replace Gliiz: it doubles your data safety and streamlines client collaboration by giving direct, permanent access to source files in your Google Drive. If you disconnect Google Drive, standard Gliiz storage remains in use.
Team & Roles#

Invite an Admin or an Editor#

Team is managed both at the account level (Team tab on the Projects page /workspaces) and directly inside each project (Settings → Team tab, strictly reserved for the Owner and Admins; hidden from Editors). Every seat you invite draws from one shared, account-wide pool.

01

Owner

The account creator. Always has full access to every project, can't be removed or reassigned a role.

02

Admin (account-wide)

Full operational access to every project the owner has, present and future. Invited from the Team area without mandatory per-project scoping. By default, an Admin cannot delete or transfer a project (the Settings "Danger" tab remains hidden). However, the owner can explicitly grant these two sensitive scopes (delete_project and transfer_project) upon invite or edit. Billing and global account settings remain strictly reserved for the owner.

03

Editor (per-project)

Access to the project selected at invitation time, limited to the granted scopes. Access is segmented by scope: three are offered by default and can be removed (content, automations, editorial); four are opt-in and sensitive (publish & connect accounts, approve, ad budget, private inbox), toggled with checkboxes at invite time. Approving an item in the approval queue requires the “Approve” scope (rejecting stays possible with automations), and committing ad spend requires “Ad budget”. A member with no scope views the project (operations, reviews, brand memory) without changing anything. If the Editor already has their own account, the shared project appears in their own workspace with a "from workspace X · Editor" badge; all work draws from the inviting owner's credit pool, and the owner's private usage/credit figures stay hidden from them.

DetailHow it works
Seat poolOne shared cap per account: the owner counts as the first seat, then every distinct Admin or Editor (active or pending) counts as one more, regardless of how many projects they touch.
Extra seatsRun out of seats on your plan? Buy more anytime from the Marketplace no plan upgrade required.
InvitationInvitations can be sent either from the global Team area (/workspaces) or directly from project settings (Team tab, reserved for the Owner and Admins). Specify an email, a role (Admin with optional sensitive scopes, or Editor with project selection and access scopes). The invitee must sign in or create an account with the invited email address, then accept the invitation to gain access.
Permission scopesAn Editor's access is segmented: content, automations and editorial are offered by default and can be removed; publishing/connecting accounts, approving, ad budget and the private inbox are opt-in, sensitive checkboxes (they expose OAuth tokens and DMs). The owner or an Admin manages them. Approving an item in the approval queue requires the “Approve” scope (rejecting stays possible with automations), and committing ad spend requires “Ad budget”. A member with no scope views the project (operations, reviews, brand memory) without changing anything. Each scope also carries its read surfaces: the project's Analytics follow the content scope, the automation approval queue follows automations, and the Inbox auto-reply knowledge base follows inbox.
Shared billingEverything a member generates on a project is billed to and capped by the project OWNER's credit pool not the member's own account. Attribution is kept per action.
TraceabilityThe Team tab shows each member's monthly credit total (with a colour), a per-member credit history down to each generated asset, and an Activity log of sensitive non-credit actions (renames, brand config, member changes). These figures are visible to the owner and Admins only.
Owner-only actionsManaging billing, subscriptions, and global account settings is strictly reserved for the account owner. Project deletion and transfer are disabled by default for collaborators; however, the owner can explicitly grant the sensitive scopes 'delete_project' or 'transfer_project' to an Admin (which unlocks the respective actions in the Settings Danger tab). Editors can never delete or transfer a project.
Managing a memberResend a pending invite, adjust scopes (via the 'Edit permissions' action), or remove access from the action menu on their row. The Owner row has no action menu.
Detailed Permission Scopes Matrix#

Security Scopes: Editor vs Administrator#

Gliiz applies the principle of least privilege. Every collaborator receives permissions tailored strictly to their responsibilities. Sensitive actions (direct social network access, confidential direct messaging, project deletion, or ownership transfer) are isolated and require explicit opt-in.

1. Per-Project Scopes (Editor Role)

When inviting an Editor to a project, three fundamental scopes are offered by default to enable immediate collaboration; they can be unchecked, and a member with no scope views the project without changing anything. Four sensitive scopes require explicit opt-in checkboxes from the owner or admin.

ScopeStatusGranted Surfaces & ActionsSecurity Rationale
Contentcontent
Offered by defaultCreate, edit and delete visuals, flyers, carousels, videos and VIBE. View project performance analytics.Creative work isolated to the project. Grants no access to social accounts or private messages.
Automationsautomations
Offered by defaultCreate, configure and activate automation workflows. Reject posts in the collaborative approval queue (approving requires the Approve scope).Controls pre-publication logic inside Gliiz. Live delivery to social channels additionally requires the publish scope.
Brandeditorial
Offered by defaultConfigure brand identity: Brand Voice, typography, colour palettes, logos and guidelines, the art direction, as set at onboarding.Ensures brand consistency and guides AI generation without exposing external resources.
Publishing & accountspublish
Sensitive · Opt-inConnect/disconnect social accounts (LinkedIn, Instagram, TikTok, Facebook, X, etc.) and publish live or scheduled posts.Sensitive (Opt-in): accesses the owner's OAuth tokens and allows broadcasting content publicly to official channels.
Approveapprove
Sensitive · Opt-inApprove or reject items in the approval queue. The approved version is what goes out: a later edit is flagged and does not go out without a new approval.Sensitive (Opt-in): decides what is published in the brand's name. Granted automatically to members who already held publish.
Ad budgetbudget
Sensitive · Opt-inCreate or resume a paid ad (Meta, Google, TikTok, LinkedIn). Pausing it remains possible with publish.Sensitive (Opt-in): commits money. Granted automatically to members who already held publish.
Inboxinbox
Sensitive · Opt-inRead and reply to direct messages (DMs), comments, trigger AI replies, and edit the auto-reply knowledge base.Sensitive (Opt-in): grants access to confidential, private conversations with prospects and customers.

2. Admin Sensitive Permissions (Account-wide)

An Account Admin holds operational access across every project on the account by default. However, the two critical and destructive actions below remain strictly denied until the owner explicitly grants these scopes.

PermissionDefault StatusUnlocked ActionImpact & Risk Level
Project deletiondelete_project
Disabled by defaultUnlocks the permanent project deletion button in the project Settings Danger tab.Critical: irreversible action that erases all project data, media, videos, automations and statistics. The Danger tab remains hidden from unauthorized Admins and Editors.
Project transfertransfer_project
Disabled by defaultUnlocks transferring project ownership to another registered user in the project Settings Danger tab.Critical: legally passes project ownership to a third party. The project permanently leaves the original owner's account.

💡 Inheritance rule: The Owner implicitly and permanently holds all scopes across every project on their account. Admins hold all daily operational permissions, while Editors are strictly scoped to their assigned project and granted scopes. The two destructive actions (project deletion and transfer) are never accessible to Editors under any circumstance.

Annotate a visual and review together#

Annotations: say WHERE, not just what#

Feedback on a visual gets lost when it stays a sentence: "the logo is too small" says neither which one nor where. An annotation is a comment placed ON the image, at a precise point. Click the visual, write the remark: it appears as a numbered pin the creator finds at exactly the same spot, on their screen and on yours.

Where to annotate. In the Library, by opening a visual full screen. And in the review screen: a pending publication opens for review, where you annotate then decide without leaving the page. A badge on the thumbnail shows how many remarks are still open, so you never approve without knowing someone wrote to you.

If the visual is regenerated. The image changes, but the remark keeps its meaning. It is neither deleted nor left pointing at random: its pin is flagged as placed on an earlier version. The text stays readable, and you know what to do with it.

Who can annotate : The Owner, Admins, and Editors holding the Content scope. Replies are one level deep: a reply always attaches to the original remark, never to another reply. Marking a remark resolved removes it from the counter without erasing the exchange. Every new annotation notifies the team in real time, with no need to reopen the page.

Mentions and notifications beyond the app : Type @ while writing a remark to bring up the project's teammates and mention one. Beyond the live in-app notice (for anyone already working on that visual), three people get notified even while offline: the visual's author when a new thread opens on it, every participant in a thread when someone replies, and anyone mentioned with @. The notice goes out by email (in the branded template, in each person's own language) and, if their Telegram is connected through Turbo, by Telegram message, never to whoever just wrote the remark.

Transferring a project or the workspace#New

Two transfers, two mechanisms#

The recipient is given by User ID or by email address. Transferring ONE project and transferring the WHOLE workspace work differently.

  • Transferring a project: if the recipient has an account, they get a request to accept or decline (by email and in the app). If they have reached their plan limits, the transfer is not refused: by accepting, they pay for the extra room (2 credits per project, 1 per social account), shown before they decide. Declining costs nothing.
  • Transferring a project to an address with no account: the account is created, the project is moved right away and the person gets a temporary password by email.
  • Transferring the workspace to an address with no account: the account itself changes owner, like an email change. Projects, credits, plan, subscription, renewal dates and invoices stay the same; the new owner gets a temporary password.
  • The previous owner loses all access: sessions closed, passkeys, two-factor, Google sign-in and Turbo removed, API keys, MCP access and payout numbers cut off. Their old address is notified.
  • A temporary password must be replaced at first sign-in: no page opens before that.

Money collected stays with whoever sold: a project whose wallet holds money (available or pending), a withdrawal in progress or a customer payment in progress cannot be transferred. Withdraw the balance first. After the transfer, payment collection is turned off until the new owner turns it back on.

Plan Limits#
FeatureFreeStarterProAgencyEnterprise
Projects131030∞
Social Accounts1520∞∞
AI credits6 (one-time)80/month200/month600/month∞/month
Included emails/month01005002000∞
Prospecting searches/month21560200∞
AI replies/month (one shared quota: Inbox, comments, all agents)050013003500∞
Automations031030∞
Team seats1125∞
Turbo flows / project0125∞
Autonomous Agents (account total)1138∞
Video montage exports / 30 days330100300∞
AI texts/month10100∞∞∞
Public API keys013720
Analytics history (days)73090365365
API Access❌✅✅✅✅
White-label❌✅✅✅✅
A/B testing❌❌✅✅✅
Multi-client workspaces❌❌❌✅✅
BYOS Google Drive❌❌❌✅✅

Resource limits (projects, social accounts, agents, automations, seats) count what exists at the same time: renewing a subscription adds no slots. Extra slots are bought with credits (or in bundles for seats) in the Marketplace and stay yours after renewal. Monthly quotas (replies, emails, searches, exports) reset every month.

For a detailed pricing breakdown, credit top-ups, and currency billing, visit the Credits & Billing module.

Documentation Feedback#

Was this documentation helpful?