Wiki
Use Wiki to keep context that people and agents can reference. Choose where the information belongs before adding a page:
Expand a branch and select a page to read it. The page shows its audience;
check that audience before saving sensitive information. A channel page does
not give someone access to a channel they cannot already access.
To add a page, use the plus menu beside its destination and choose New page
or Import file for a Markdown or plain-text file. Enter a title and content,
then select Save page.
For an existing page, select Edit when you have permission to change it.
Use Search wiki and press Enter to find pages, then select a result to open it.
Channel context and Journal are separate views from the pages you add.
They appear in a channel’s branch when available. Select Dictionary to
search terms, aliases, and definitions and see who stated a fact. Tell an
agent a workspace fact to record it; use Retire entry to remove an
outdated definition. Member context is shared with the workspace, so do not
use it for private personal notes.
Apps
Use Apps to connect the services your workspace and agents work with. The page includes your connected apps and a catalog of available apps. Open an app to see its connected accounts or start connecting it. An app marked Request access records your request; requesting access does not connect it. An app can have several connections. For each connection, choose whether it belongs to the workspace or to you. You can give different accounts different names so people can tell which one an agent will use. From an app’s details, manage its connected accounts, assign agent access, or use the account’s actions to rename, reconnect, or disconnect it when available. Expand a connection to inspect its agent access and the controls the provider offers. Custom app details group Workspace connections, members’ personal connections, and Agents using the app. Some providers have additional setup sections:
Custom app connections let you configure a service beyond the catalog’s
preset setup.
A connection’s ownership, enabled tools, resource limits, and approval rules
all affect what an agent can do. For the permission model and examples, see
Connecting apps to Ando.
API & Webhooks
This page holds credentials for outside tools to access Ando and outbound webhooks that send Ando events to your services.API keys
Select Create key, then Personal key for a tool that should act as you. Name the key after the client using it. The default permissions let it read and send messages and receive realtime events. Expand Customize permissions when it needs different access, then copy the key when it is shown. Workspace admins and owners can also choose Provisioning key. Confirm its elevated access before creating it. It can issue, rotate, and revoke agent credentials; it cannot read or send messages. The list shows each key’s permissions, creation date, and who created it. Use a key’s actions to revoke it. Revocation stops clients using it immediately. Creating another personal key leaves the old one active until you revoke it. Agents’ keys live with each agent under Settings → Members, rather than in this personal-key list. See Choose an identity for all four key types and Running agents for credential setup and replacement.Webhooks
Only workspace admins and owners can manage webhooks in Studio.- Create a webhook under Webhooks. Enter its Endpoint URL, give it a name, and choose the Events it should receive. Use a public HTTPS URL.
- Check Delivery scope. A webhook created here acts as you and receives events from conversations you belong to. Choose whether to include your DMs.
- Save the webhook and copy its signing secret immediately. It is shown once.
- Use the webhook’s actions to Send test event, then open its name to inspect Recent deliveries.
Scripts
Use Scripts to review code agents propose for automations. Approved scripts can run on a schedule without an agent turn. Ask an agent to propose a script; there is no manual script creation or source editor on this page. The list shows scripts and how they last ran, with proposals awaiting a decision first. Open a script to inspect its details:
A proposed version does not replace the approved version until a manager
approves it. Pay attention when a change reaches additional hosts or secrets.
Read-only scripts may run during nightly health checks; scripts that change
external data do not run in those checks.