What Oleria discovers
- User accounts and profile attributes synced from InVision’s team directory.
- Team membership across your organization.
Prerequisites
- Admin access in InVision with permission to generate an API token.
- Admin access on the Oleria platform to add a new integration.
The exact location of these settings can change over time. If the steps below don’t match what you see, refer to InVision’s own API documentation.
Get your SCIM credentials from InVision
1
Generate an API token in InVision
Sign in to InVision as an admin, go to Team Settings → API, and generate an API token.
2
Copy your SCIM Base URL and Authentication token
Copy both values before you leave the page - you’ll paste them into Oleria in the next section:
- SCIM Base URL - the HTTPS API endpoint for your InVision team.
- Authentication token - the API token you generated.
Copy the token now. Many applications display it only once. Store it securely and rotate it per your organization’s security policy.
Connect InVision to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations, then select the InVision tile.
2
Complete the connection form
Select Continue and fill in the connection form:
3
Save the integration
Select Connect to validate the credentials and save the integration.
Verify the integration
Confirm the new instance appears in your Oleria workspace under Connected Integrations with a status of Healthy. Oleria syncs users and teams from InVision on the standard SCIM provisioning schedule once the initial sync completes.If InVision rotates your API token, update the Authentication token in Oleria by editing the integration.
Governance actions
Oleria can also invoke lifecycle actions in InVision when the token you provide has write access:- Enable or disable a user account
- Add or remove a user from a group
- Create a new user or group
Many teams start with a read-only token for visibility, then grant write access once they’re ready to automate remediation in InVision.

