Administer your account in the console
Status: Upcoming — not yet available.
Section: DOC-CP-console-administration#overview.
Bring a teammate into the project they will administer while keeping the application’s service integrations independently owned. The recipe starts with your administrator session, adds the teammate with the access their task needs, and ends by confirming their accepted membership and the application’s continuing operation.
You need the organization’s console sign-in route, authority to manage the intended project, and a teammate who can accept the invitation. Use the separate key-rotation and operational guides when the job is to change an existing integration rather than invite a person.
Available today: Console pages and permissions depend on your account. Expanded workspace/project selection, additional roles, SSO administration, audit and privacy workflows are planned. If an action below is absent, use its linked API guide where available or ask your administrator for the supported route.
1. Start from the administrator’s account
Status: Upcoming — not yet available.
Section: DOC-CP-console-administration#sign-in-and-account.
- Open the console link provided by your account administrator through your established account channel.
- Use the human sign-in method enabled for that deployment. Application API keys and your application's end-user JWT are not substitutes for a team-member console session.
- Confirm the signed-in person and the account you intend to administer before viewing or changing resources.
- Check the capabilities and permissions available to that person. If the required action is absent or denied, request the specific access needed from your administrator.
Use the sign-in method issued for your account. Ask your administrator whether SSO is enabled before attempting to configure it; the additional options described here are planned.
If your session expires or cannot refresh, sign in again to continue. Do not send session tokens or API key values when requesting help.
2. Choose the application the teammate will manage
Status: Upcoming — not yet available.
Section: DOC-CP-console-administration#scope-selection.
The console shows the workspace, project, test/live mode and any selected application customer alongside your work. The current public API still uses the legacy default project and does not offer a public test mode. Use only the selections enabled for your account; changing a label or request header does not create isolation.
To work in another project or customer account:
- Choose the workspace and project you are authorized to administer.
- Choose test or live, plus the customer where relevant. An unassigned selection shows records that do not belong to a customer.
- Review the records loaded for that selection.
- Recheck scope when opening a saved link or returning to an old tab.
After you switch, the console shows the selected account’s records. Updates from the previous selection cannot replace the new view. If the visible resource and selected scope disagree, stop the action and report both identifiers through your account's support channel. Selecting all customers is an authorized read view, not permission for a bulk mutation.
3. Invite the teammate and preserve service ownership
Status: Upcoming — not yet available.
Section: DOC-CP-console-administration#people-and-credentials.
For current key issuance or rotation, follow Managing API keys through the enabled management surface or your account administrator.
To give a teammate access:
- Select the intended workspace or project and identify the person to invite.
- Choose the minimum role needed for their tasks and distinguish a direct project assignment from inherited administrator access.
- Invite the teammate. They verify their identity and accept the invitation before becoming a member.
- Review the accepted membership and the projects the teammate can access.
- When their role changes, review their resulting access and any service credentials that need attention.
Keys belong to their project and service. Record the application/service owner, scope, expiry and responsible contact. The creator remains an audit record; removing that person’s access leaves independently owned service integrations running. If a secret was exposed, make a separate authorized rotation or revocation decision. These expanded ownership controls are not yet available.
Human team membership and your application's end-user directory are separate. Creating or editing an end user does not invite that person to administer the workspace. Changes to branding, names or email domains do not grant access.
For offboarding, remove the person’s management access and review any credential exposure as a separate decision. Independently owned service keys continue to support the application; rotate an exposed secret through its owning workflow, then verify the integration with the replacement.
4. Confirm access and unfinished setup
Status: Upcoming — not yet available.
Section: DOC-CP-console-administration#lists-and-status.
After the teammate accepts, confirm which project access they have and whether any required connection setup is still pending. Keep membership status separate from integration readiness. If they can sign in but cannot perform the assigned task, compare the task’s required access with their effective assignment before granting more.
When checking the teammate’s membership list, confirm the selected project and follow all result pages before concluding an assignment is absent. A partial page is not a complete access review.
For a separate dashboard or usage investigation, inspect freshness and coverage before treating missing data as zero activity. Trace and observation reads describe the filters and cursors for that workflow.
Provisioning, connection setup and cleanup can finish in separate steps. If activation fails after a connection is created, recover that connection’s setup. Keep the operation or resource reference before retrying an administrative write.
Recover an interrupted invitation or account change
Status: Upcoming — not yet available.
Section: DOC-CP-console-administration#change-recovery.
If a key, permission, connection, payment or deletion action loses its response:
- Keep the original operation reference, target resource and submitted change.
- Refresh or reopen the owning capability's status, using the same account and scope.
- Determine whether the change completed, failed, remains pending or needs a specific follow-up.
- If the outcome is unknown, ask the responsible account contact to reconcile it before submitting the change again.
The console saves progress and outcomes so you can return to an interrupted change. For now, confirm the resource's actual state or ask your account contact; a spinner, success toast or browser error alone does not settle the result.
Use this information in an administration request:
Signed-in account identity (no token):
Workspace / project / mode shown, where available:
Task and target resource reference:
Operation reference, if returned:
Last observed status and time:
Requested access or recovery action:
When requesting help from Travila staff, agree which account, resources and actions the support request covers. Support access requires separate authorization and does not give your teammates access to another customer's content. Expanded support, audit and privacy controls are not yet available.
Variants: rotate a key, inspect a connection or review usage
Status: Upcoming — not yet available.
Section: DOC-CP-console-administration#administration-tasks.
Use these guides for the capability-specific workflow and API reference. A linked API operation does not imply that a corresponding console action is available.
| Task | Continue with |
|---|---|
| Obtain an application credential, select scopes or rotate a key | Authentication and API keys and Scopes and permissions |
| Set up an application or plan workspace membership | Workspaces and projects |
| Understand usage, an account restriction or payment status | Billing and spend |
| Prepare an Enterprise offer, onboarding or a plan change | Commercial agreements and invoicing |
| Manage profiles or inspect conversations | Managed Agents |
| Inspect traces, observations, scores or datasets | Evaluation |
| Configure webhooks or tools | Integrations |
| Store credentials used by a connection | Project secrets |
| Request audit evidence, export or erasure | Governance and privacy |
Document ID: DOC-CP-console-administration. Section identities and revisions.