> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-studio/catalog-manager/access-managment.md). # Access Managment The Access screen is the central place to see and manage which artifacts in your catalogs have explicit access restrictions. Open it by clicking Access in the left panel of the Catalog Manager, or via the Manage link in the Access Rules card on the Overview screen.
### Restricted Resources List The main area lists every artifact across all catalogs that has a Restricted access rule applied to it. Only artifacts with explicit restrictions appear here — Open artifacts are not shown. Each row in the list shows: * Name - The artifact name and the catalog it belongs to (shown below the name). * Type - The artifact kind (e.g., Dashboard, Dataflow, AI Skill) * Roles - Pill badges showing each role that has been granted explicit access, each labelled with R (Read) or W (Write) to indicate the access level * Edit icon - Opens the Item Access panel to view or change role permissions for that artifact ### The Item Access Panel Click the edit icon on any row to open the Item Access panel for that artifact. The panel shows the artifact name, type, and catalog at the top, along with its current restriction status.
#### Role Permission Table Every role in the tenant is listed in the panel, with four access level options shown as selectable buttons for each role:
LevelWhat the Role Can Do
No accessThe role cannot see or use this artifact at all
UseThe role can invoke or consume the artifact (e.g., run a dataflow, view a dashboard) but cannot read its definition
ReadThe role can view the artifact's full definition and configuration, in addition to using it
WriteThe role has full access — it can use, read, and modify the artifact
### How Access Rules Fit Together The default state for every artifact is open to the entire tenant. A restriction is an exception — you add one when you need to limit visibility or editing rights to specific roles. The Access screen surfaces only those exceptions, keeping the view focused and manageable.
ScenarioWhat to Do
You want everyone in the tenant to use an artifactLeave it Open (no rule needed — it will not appear on this screen)
You want only specific roles to access an artifactSet it to Restricted and grant the relevant roles the appropriate level in the Item Access panel
You want to check what a specific role can seeUse the Role Lookup panel and select that role
You want to remove all restrictions from an artifactOpen the Item Access panel and click Make unrestricted
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://documentation.astera.com/astera-studio/catalog-manager/access-managment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.