Quick answer
Go to Integrations in the OptiTech Console and select the integration. Its detail page shows everything about the connection: status and last successful sync, the account or tenant it's connected to, the exact permissions granted, the credential type and its age, and the list of checks the integration feeds. This page is both your operational view and your documentation of what the connection can access.
What each section tells you
- Status and last sync: green with a recent timestamp means evidence is flowing. Errors and warnings link to sync troubleshooting.
- Connected account: which Entra tenant, AWS organization, or GitHub org the integration reads from, so multi-tenant organizations can verify they connected the right one.
- Permissions: the granted scopes, stated in the provider's own terms (for example, which Graph API scopes). This is the section to show a security reviewer asking what the integration can reach; the answer should be read-only scopes, per the agentless collection model.
- Credential info: type (OAuth app, service account, API key), created date, and rotation status, feeding the credential rotation routine.
- Checks fed: every automated check that depends on this integration, with links to the controls they verify. This is also your impact preview for disconnecting: you see exactly which controls would lose monitoring.
Why these details end up in your compliance documentation
Your compliance platform's integrations are themselves access relationships that your program should account for. The integration page gives you the facts for your records: OptiTech appears in your supplier register, the granted scopes belong in your access documentation, and the connection is part of the answer when a customer asks who can read your tenant data. Convenient, then, that the page is exportable like everything else.
Get a personalized walkthrough of automated compliance for your team. No commitment required.