Workspaces & Permissions
Explains how GLIK Cloud uses organization-scoped workspaces to manage access, invite users, and configure role-based permissions across apps, templates, and memory.
Last updated
Was this helpful?
Explains how GLIK Cloud uses organization-scoped workspaces to manage access, invite users, and configure role-based permissions across apps, templates, and memory.
Last updated
Was this helpful?
uses organization-scoped workspaces to manage apps, users, and permissions. Each workspace is associated with a specific organization, and every app, template, or memory object is scoped within that org.
To start, you’ll either:
Create a new organization from the workspace switcher
Or join an existing one via an invite
Organization slugs determine the subdomain used in your GLIK Cloud URL (e.g.
rivalz.glik.ai
)
Admins and Owners can manage users from the Members tab in the Organization Settings.
You can invite teammates via email and assign their role on invite.
Roles available:
Normal – Can use apps but not edit system settings
Admin – Can manage users, apps, memory, and integrations
Owner – Full access to everything in the workspace
🔐 Only Owners can transfer ownership or delete an organization.
Each organization also has branding and identification settings:
You can:
Upload a logo
Set organization name and slug
Specify country for compliance/auditing