Permissions & Scope
Who has access to What ..
Communities, Permissions & Scope
As you know ..
A Community is a custom role that is used to fine-tune access to specific actions or Data Catalog assets. For example, you can use a community to restrict access for a group of users to a subset of glossaries and data sources.
The AdventureWorks2022 database contains multiple schemas representing different business domains:
HumanResources: Employee data, departments, payroll
Sales: Orders, customers, territories, sales staff
Production: Products, inventory, manufacturing
Purchasing: Vendors, purchase orders, procurement
Person: Contact information, addresses, demographics
Let's walk through an example of how to apply these restrictions ..
x
x
Sales
Sales Schema Data Source Creation
When connecting to the AdventureWorks2022 database, administrators would create a dedicated "mssql:adventureworks2022-Sales" data source. During the "Ingest Schemas" process, click Ingest Schema, select the following schemas:
Sales -
Person -
and then click Ingest Schemas.
x
Log into Data Catalog:
Username: [email protected]
Password: Welcome123!
Click: Management in the left navigation menu.
Click: Communities (Users & Communities tile).
Select: AdventureWorks_Sales_Analytics > Edit
Scroll down to Scope
Select: Data Sources & click: +
Select: mssql:adventureworks2022-Sales & uncheck All
Click: Done & Save.
While you're here .. Edit the Scope: Data Sources for AdventureWorks_System_Administrators from All to: mssql:adventureworks2022.
We've now set the Data Sources Scope for the Sales Analysts .. we'll be back to set the others ..!!
Finally .. test by logging in as:
Username: [email protected]
Password: Welcome123!
Last updated
Was this helpful?