Connected apps and permissions

Begin with the task you want to accomplish, then connect the service and account that task needs. A work account and a personal account can have very different audiences and data.

• Check the account identity during the connection flow.
• Review the permissions requested by the service.
• Enable the apps and tools relevant to your work.
• For organizational accounts, follow your organization’s approval process before connecting.

Finding an email and sending an email have different consequences. Relam’s connected-app actions identify the account and operation involved. External writes in the plugin flow require your approval, and account access is checked again when the action runs.

Before approving, review the destination, account, content, and intended effect. If the connected account changes, the operation needs a fresh review.

Compatible MCP servers can extend the tools available in a workspace. The server you choose has its own operator, capabilities, and data practices. Review these before connecting or approving a tool call.

• Identify who operates the server and what it can access.
• Understand which information a call sends outside Relam.
• Review actions that write, publish, or change information.
• Reassess the connection when the server or your use case changes.

Check your connected accounts when a project ends or a role changes. Review access in Relam and in the connected service; they are separate places to manage permissions.

When an operation reports an error, check the destination service before retrying a consequential action. An interrupted response alone does not tell you whether an external change occurred.

• Workspace data controls
• Working with AI output
• Enterprise evaluation

Return to the Trust Center