Skip to main content

Access Management

Access Management gives workspace administrators fine-grained control over who can access what — from data layers and compute engines to PII and budget limits.


Overview

Navigate to Access Management in the sidebar. This is an admin-only surface.

The main view shows a table of user groups with inline-editable fields:

ColumnDescription
Group nameLogical grouping of users (e.g., "Analytics Team," "Data Engineering")
OwnerAdministrator responsible for this group
UsersMembers of the group
Budget limitMaximum monthly compute spend allowed
Budget usedCurrent spend against the limit
Allowed enginesWhich compute engines the group can use
Bronze accessWhether the group can access bronze layer tables
Silver accessWhether the group can access silver layer tables
Gold accessWhether the group can access gold layer tables
PII accessWhether the group can access personally identifiable information

Managing groups

Editing group settings

All fields in the table are inline-editable. Click any cell to modify:

  • Add or remove users from a group
  • Adjust budget limits
  • Toggle layer access (Bronze, Silver, Gold)
  • Enable or disable PII access
  • Change allowed compute engines

Budget monitoring

The Budget used column shows real-time spend. When usage approaches the limit:

  • A warning indicator appears on the row
  • Anomaly detection flags unusual spending patterns

Access model

Zingle uses a layer-based access model:

LayerTypical access
BronzeRaw data — restricted to data engineers
SilverCleaned data — accessible to senior analysts
GoldBusiness-ready data — broadly accessible

PII access is an orthogonal control. A group might have Gold access but not PII access, meaning they can query gold tables but PII columns are masked or hidden.


Best practices

  • Principle of least privilege. Start with Gold-only access and expand as needed.
  • Set budget limits early. Prevent runaway compute costs before they happen.
  • Review PII access quarterly. Ensure only the right people have access to sensitive data.
  • Use groups, not individual permissions. Group-based access is easier to audit and maintain.