Describe the outcome
State the request the role handles, what information it may use, what it should return, and when it must stop and ask for help.
← Back to homeDocumentation
A guide to the AI workforce you control.
Explore how a role moves from request to daily work, and where your team sets its instructions, connections, model and control boundaries.
Set up an AI teammate around a real workflow.
Start with one bounded job. Write down what a good result looks like, which systems the role needs, who owns it, and which decisions require a person. Use this checklist with your workspace administrator.
Name an accountable owner
Choose the person responsible for instructions, access decisions, review points and changes to the role.
Grant only needed access
Select the tools and records needed for this workflow. Check the permissions of the connected account and the actions available to the role.
Keep people in important decisions
Set clear review points for consequential work. Test representative requests and confirm the role handles missing information safely.
Watch activity and spend
Review available activity records, model usage and estimated cost. Revisit the role when its work, tools or risk changes.
Know where to review each decision.
Identity and accessWorkspace roles determine who can request, inspect, manage and change sensitive settings. Read security details →
KnowledgeThe employee and agent knowledge experience is in development. Read its current scope →
Connections shown on the siteSlack, Microsoft Teams, WhatsApp, Gmail, Google Drive, Outlook, Excel, OneDrive, SharePoint, Salesforce, HubSpot, Zendesk, Apollo, Hunter, Xero, Tally, Notion, Confluence and Jira, with Serper.dev available through Web Search. Availability and supported actions depend on workspace setup and approved credentials.
Network accessNetwork access allows destinations unless a super admin adds a block rule. Review current rules during setup; this is not a default-deny allowlist. See the network access details →
Activity and spendInspect available agent activity, model usage and estimated cost in the Command Centre. Cost is an estimate and may differ from provider invoices.
Data pathUseGlic operates its workspace in the EU region by default, and you can set your organisation's data region in workspace settings. Review the security page →
The current subprocessor list is published on the subprocessors page.
Already have a workspace?
Sign in to review your roles, connections and activity.