Veritas Alta™ SaaS Protection Administrator's Guide
- Introduction to Veritas Alta™ SaaS Protection
- EDB and EDB compliance
- Active Directory synchronization
- Manage users and roles
- API permissions
- Add connectors
- Overview of adding connectors
- Add Exchange Online connectors
- Configure the capture scope for Exchange connectors
- Configure the capture scope for Exchange connectors
- Add SharePoint Online connectors
- Configuring the capture scopes for SharePoint connectors
- Add Teams site collections connectors
- Add OneDrive connectors
- Add Teams chat connectors
- Add Audit Log connectors
- Add Google Drive connectors
- Add Gmail connectors
- About the Salesforce connector
- Add Entra ID (Azure AD) connectors
- Add Box connectors
- Add Email/Messages
- Apps Consent Grant Utility
- Add Retention policies
- Perform backups
- Manage backed-up data
- Perform restores using Administration portal
- Restore SharePoint/OneDrive/Teams Sites and data
- Restore Teams chat messages and Teams channel conversations
- Restore Box data
- Restore Google Drive data
- About the Salesforce Data, Metadata, and CRM Content restore
- Limitations of Salesforce Metadata backup and restore
- About Entra ID (Azure AD) objects and records restore
- Perform restores using Export Utility
- Restore dashboard
- Install services and utilities
- Discovery
- Add Tagging polices
- Add Tiering policy
- General administrative tasks
- Manage Stors (Storages)
- Managing Scopes
- Known Issues
About Scopes
Scope is a mechanism that allows regional administrators to manage connectors, perform admin restores, and so on only for the region to which they have been assigned, without having access to the underlying OAuth Client Secrets. Scopes make it simple to grant regional administrators access to the connectors and admin restore for their region. | See Enabling Scopes. __________________________________ See Configuring Scopes. __________________________________ See Using Scopes. |
The following planning is required to enable Scopes:
Determine the administrators for each Scope.
Determine the number of connectors and App Registrations required.
To ensure the best performance:
Use dedicated applications for each Scope and Connector.
Do not use the same application for Exchange and SharePoint connectors.
Per Scope, you can only create one Exchange connector and one SharePoint connector. If multiple Exchange or SharePoint connectors are required, multiple Scopes should be created.
It can be helpful to give the application a name that is a combination of the Scope and Connector names. It ensures that applications are not reused across connectors.