Mostly read-only
Most permissions only let CtrlConnect read information so it can show reports, queues, and dashboards.
Changes only when you ask
CtrlConnect changes your tenant only when an admin takes an action, or when an automation policy you created runs.
Every change is logged
Each change appears in the audit log, showing whether a person or an automated job made it.
What CtrlConnect never does
No reading email. CtrlConnect does not ask for permission to read mail messages.
No sending mail from your tenant. Review emails come from
noreply@ctrlconnect.nl, a CtrlConnect mailbox in our own tenant. Your consent screen never includes permission to send mail as your users.No opening your files. CtrlConnect reads file and folder names, locations, and who they are shared with. It never downloads or opens file contents.
No passwords or secrets. You sign in with Microsoft. CtrlConnect sees which sign-in methods a user has registered, never the methods themselves.
Every permission, explained
Microsoft names each permission by what it allows, for exampleUser.Read.All means “read all user profiles”. The consent screen Microsoft shows you uses the same names as this page.
- Reading your tenant
- Changes you make
- Exchange and templates
How your access stays protected
You approve it in Microsoft
Consent happens on Microsoft’s own screen. CtrlConnect only receives the permissions your Global Administrator approves there.
Separated from the web app
The CtrlConnect web app never holds your Microsoft credentials. Changes are sent to Microsoft by a separate background service and recorded in the audit log.
People and jobs kept apart
Automated jobs are always recorded as jobs, never as a person, so you can always tell who made a change.
Your tenant only
Your data is kept separate from other customers’ data at the database level.
Review or revoke access at any time
CtrlConnect appears in your tenant as an enterprise application. You stay in control of it.1
Open the Microsoft Entra admin center
Go to Enterprise applications and select CtrlConnect.
2
Review the permissions
Open Permissions to see exactly what was granted. It matches the list on this page.
3
Remove access if you need to
Delete the application to revoke all access at once. CtrlConnect can no longer read or change anything in your tenant.
Common questions
Why does CtrlConnect use application permissions?
Why does CtrlConnect use application permissions?
CtrlConnect keeps your reports and queues up to date in the background, even when nobody is signed in. Microsoft requires application permissions for that kind of background access.
Do we have to grant everything?
Do we have to grant everything?
No. If a permission is missing, only the feature that needs it is affected. That feature shows not read or names the permission it needs, and the rest of CtrlConnect keeps working.
Will we need to approve new permissions later?
Will we need to approve new permissions later?
Only if a new CtrlConnect feature needs one. Microsoft asks a Global Administrator to approve it first, and nothing new is granted until you do.
Who in our organization needs to approve?
Who in our organization needs to approve?
A Global Administrator. If that isn’t you, use Request approval during setup to send them the request. See Connect your tenant.