Administer your workspace
Understand the organisation controls for connections, skills, Twin knowledge, access, and runtime operations.
The Admin menu brings together organisation-level controls. What you can see depends on your role and which capabilities your organisation has enabled.
Choose the right area
| Area | What it is for |
|---|---|
| Plugins | Connect approved services and check their setup or sync state |
| Skills | Manage reusable instructions and capabilities available to agents |
| Automations | Review scheduled Sessions and Inbox routing rules |
| Twin | Review source coverage, proposed changes, and governed business knowledge |
| Memory | Review durable context and any approval work available to your role |
| Electric runtime | Inspect technical agent operations during an implementation or support task |
Most organisation administrators will spend their time in Plugins, Automations, and Twin. Runtime controls are intended for implementation and support work.
Connect a business service
Open Plugins, choose the approved service, and follow its protected setup flow.
Keep credentials in the provider or workspace setup screen. Do not paste a password, access token, client secret, or cookie into a Session.
After setup, distinguish the states carefully:
- Needs action means a person must complete a step.
- Checking means verification is still running.
- Ready means the connection has supplied usable evidence.
- Failed means the reported problem needs attention.
Saving settings is not the same as a ready connection. Confirm the provider state and test a real, permitted workflow.
Manage what agents can use
Skills give agents reusable ways to perform work. They are different from Twin knowledge:
- a Skill helps an agent carry out a task;
- Memory keeps useful context within its approved scope; and
- the Twin holds reviewed, versioned business meaning.
Keeping these separate makes it easier to understand why an agent acted and which business definition supported its answer.
Review the Twin
Open Admin → Twin to see the current state, source coverage, proposed changes, governed datasets and relationships, and recurring user demand.
Use the review and publication guide before approving business meaning or making it available more widely.
What it knows shows the business views constructed from connected evidence. It is not an authoritative publication, activation, or external-access readiness screen. Ask your implementation lead to confirm those release gates before treating a visible dataset as available to another AI tool.
Manage people and access
Organisation and account controls appear only when your sign-in mode and role allow them. Invite people through the protected workspace control provided to you; do not share another person's invitation or alter organisation addresses by hand.
When someone cannot see an area, first check their organisation and role. Do not widen access simply to work around a missing connection or incomplete setup.
Ask for help before changing runtime controls
Electric runtime and low-level technical settings can affect active agent work. Use them only as part of an agreed implementation or support process.