- PrivaceraCloud Release 4.5
- PrivaceraCloud User Guide
- PrivaceraCloud
- What is PrivaceraCloud?
- Getting Started with Privacera Cloud
- User Interface
- Dashboard
- Access Manager
- Discovery
- Usage statistics
- Encryption and Masking
- Privacera Encryption core ideas and terminology
- Encryption Schemes
- Encryption Schemes
- System Encryption Schemes Enabled by Default
- View Encryption Schemes
- Formats, Algorithms, and Scopes
- Record the Names of Schemes in Use and Do Not Delete Them
- System Encryption Schemes Enabled by Default
- Viewing the Encryption Schemes
- Formats, Algorithms, and Scopes
- Record the Names of Schemes in Use and Do Not Delete Them
- Encryption Schemes
- Presentation Schemes
- Masking schemes
- Create scheme policies on PrivaceraCloud
- Encryption formats, algorithms, and scopes
- Deprecated encryption formats, algorithms, and scopes
- PEG REST API on PrivaceraCloud
- PEG API Endpoint
- Request Summary for PrivaceraCloud
- Prerequisites
- Anatomy of a PEG API endpoint on PrivaceraCloud
- About constructing the datalist for /protect
- About deconstructing the response from /unprotect
- Example of data transformation with /unprotect and presentation scheme
- Example PEG REST API endpoints for PrivaceraCloud
- Audit details for PEG REST API accesses
- Make calls on behalf of another user on PrivaceraCloud
- Privacera Encryption UDF for masking in Databricks
- Privacera Encryption UDFs for Trino
- Syntax of Privacera Encryption UDFs for Trino
- Prerequisites for installing Privacera Crypto plug-in for Trino
- Variable values to obtain from Privacera
- Determine required paths to crypto jar and crypto.properties
- Download Privacera Crypto Jar
- Set variables in Trino etc/crypto.properties
- Restart Trino to register the Privacera Crypto UDFs for Trino
- Example queries to verify Privacera-supplied UDFs
- Azure AD setup
- Launch Pad
- Settings
- General functions in PrivaceraCloud settings
- Applications
- About applications
- Azure Data Lake Storage Gen 2 (ADLS)
- Athena
- Privacera Discovery with Cassandra
- Databricks
- Databricks SQL
- Dremio
- DynamoDB
- Elastic MapReduce from Amazon
- EMRFS S3
- Files
- File Explorer for Google Cloud Storage
- Glue
- Google BigQuery
- Kinesis
- Lambda
- Microsoft SQL Server
- MySQL for Discovery
- Open Source Spark
- Oracle for Discovery
- PostgreSQL
- Power BI
- Presto
- Redshift
- Redshift Spectrum
- Kinesis
- Snowflake
- Starburst Enterprise with PrivaceraCloud
- Starburst Enterprise Presto
- Trino
- Datasource
- User Management
- API Key
- About Account
- Statistics
- Help
- Apache Ranger API
- Reference
- Okta Setup for SAML-SSO
- Azure AD setup
- SCIM Server User-Provisioning
- AWS Access with IAM
- Access AWS S3 buckets from multiple AWS accounts
- Add UserInfo in S3 Requests sent via Dataserver
- EMR Native Ranger Integration with PrivaceraCloud
- Spark Properties
- Operational Status
- How-to
- Create CloudFormation Stack
- Enable Real-time Scanning of S3 Buckets
- Enable Discovery Realtime Scanning Using IAM Role
- How to configure multiple JSON Web Tokens (JWTs) for EMR
- Enable offline scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Real-time Scanning on Azure Data Lake Storage Gen 2 (ADLS)
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- PrivaceraCloud
- PrivaceraCloud Previews
- Privacera documentation changelog
About data access users, groups, and roles resource policies
The Access Manager > Users/Groups/Roles page is for managing data access users, groups, and roles.
Data access users can be allowed or denied use of data stored in connected applications, as opposed to portal users, who are users that can log into your PrivaceraCloud account.
Users
You use data access users when you define resource policies. Users can be included or excluded specifically or in groups for allowed or denied access
The User Source field indicates the method of their creation or import (source).
The internal administrative "users": admin, rangerusersync, keyadmin, rangertagsync, and {OWNER} are automatically defined when your PrivaceraCloud account is created. Additional Internal users can also be created in this dialog using the +Add button dialog.
External users can be any of the following:
A data access user with the same username as the account administrator user.
A service user. A service user is automatically created by PrivaceraCloud for each connected application service and is named for the service (e.g. hive, s3, ...). Service names are reserved and cannot be reused.
Users imported via UserSync from LDAP or Active Directory.
See Connect users for information on importing users.
The Visibility field indicates if a user record is listed or available when creating or editing a resource policy with Access Manager. If a user record is visible, you can find it under Select User. If a user record is Hidden, it is not selectable. This is useful when your account has been synchronized with a user directory with a large number of users. Visibility can be set by selecting a user object row (on the left side of the table, and using the Visibility action (between +Add and Delete).
User Role applies to individual data access users: User, Admin, Auditor, or KeyAdmin}.
Use Search to filter displayed objects by a specific value. First select a column name, then a value.
User objects can be added, edited, or deleted.
Groups
Groups are collections of associated users. Users can be members of more than one group. Similar to user objects, groups are used in definition of resource policies. Groups can be included or excluded specifically or in association with other groups for allowed or denied access.
All functions for users are also available for groups: add/delete, hide/show, and search.
Roles

Witgh the Roles tab, you can create custom roles used for use when you define data access policies. Custom roles are distinct from data access imported roles and user roles.
Click +Add New Role to create a new custom role. At least one user, group, or role must be selected. Use the dropdown to select the desired users, groups, or roles. Under the column Is Role Admin, set one or more existing users, groups, or roles to be a role administrator.