Providers
Providers connect Superviso to services your organization already uses. A connector can bring in identities, privileges, resources, or directory information depending on the provider and the integration selected in Superviso.
Use a dedicated credential where the provider supports one. Grant only the access listed in the provider guide, store the credential in Superviso, and test the connection before enabling synchronization. Provider credentials are treated as secrets and are not included in the public user guides.
What each integration does
The labels on each provider card describe what its connector can bring into Superviso. Enable the capabilities you need; a provider can support more than one.
Identity Source
Keep Superviso’s user population and group membership in sync with your authoritative directory. Map directory groups to Superviso groups to give people the intended membership and access.
Example: Use Microsoft Entra or Google Workspace to keep your employee population current.
Set up Identity Source →Identity & Access
Import accounts, groups, privileges, and access assignments to inspect who has access to a connected system. These external accounts are separate from Superviso user records.
Example: Import GitHub organization membership and access information for an access review.
Explore access governance →Assets & Data
Import supported technical resources and their inventory context, then relate them to governed systems or services. Review ownership, data types, processing locations, and classification to complete their context.
Example: Collect AWS cloud resources or GitHub repositories and link them to the systems they support.
Explore assets and data →Superviso supports one authoritative Identity Source at a time. Its scope and lifecycle policy can affect existing users, including suspension and archival. SSO separately controls how people sign in; configure it independently of directory synchronization.
A Microsoft connector can use Entra for Identity Source and Identity & Access, and Azure for Assets & Data. Check the required permissions for the options you actually enable; supporting a capability does not enable it automatically or confirm that a synchronization has succeeded.
Supported providers
Amazon Web Services (AWS)Identity & Access; Assets & Data
AWS IAM Identity CenterIdentity & Access
AtlassianIdentity & Access
CloudflareIdentity & Access
FreeScoutIdentity & Access
GitHubIdentity & Access; Assets & Data
Google AnalyticsIdentity & Access
Google WorkspaceIdentity Source; Identity & Access
MicrosoftIdentity Source; Identity & Access; Assets & Data
MongoDB AtlasIdentity & Access
SentryIdentity & Access
SlackIdentity & Access
SonarCloudIdentity & Access
WordPressIdentity & Access
Configure a connector
In Superviso, open the connector settings and choose the provider. Enter the credential and configuration values from the relevant guide, select the applicable integration and collection options, then test the connection. A successful connection test confirms that Superviso can authenticate and reach the provider; the first synchronization confirms which records are available under the granted access.
If a test fails, verify that the credential has not expired or been revoked, the account or organization identifier is correct, and every required permission has been granted.