Skip to content
Tropikal Tropikal Docs

Accesses

Accesses are connected accounts or systems that Tropikal is allowed to use. Examples include Google Drive, Gmail, Calendar, a connected website, or an API account.

Connect an Access once, then choose it when a workflow step or persona function needs that account.

Why Accesses are separate

A function is what Tropikal can do. An Access is the account Tropikal can use to do it.

For example:

  • A Google Drive function can list or read files.
  • A Google Drive Access is the connected Google account and approved Drive scopes.

Keeping them separate makes setup easier and keeps tokens out of functions, workflows, and persona instructions.

Where to manage them

Open Accesses in the workspace sidebar. From there you can:

  • see connected accounts and websites;
  • open an Access detail page;
  • reconnect an expired account;
  • deactivate or delete access that should no longer be used;
  • review which personas or workflows use the Access.

Using Accesses in workflows and personas

When a workflow step or persona function needs a connected account, Tropikal prefills an existing matching Access when one is available. The Access picker appears directly under the function picker, so setup stays focused on one choice: which account should this function use?

If none exists, choose New access from the setup flow. After the account is connected, Tropikal returns you to the workflow editor or persona setup screen you came from.

Using Accesses with personas

When you add a function to a persona, choose the Access that function should use. Tropikal then sets up the permission behind the scenes. Grant only the accounts the persona actually needs.

Example:

  1. Connect a Google Drive Access.
  2. Add a Google Drive function to the support persona.
  3. Choose the Google Drive Access in the picker.
  4. The persona can now answer with approved Drive-backed function calls.