12.2 Row-Level Security, Schedules, Subscriptions & Alerts
Key Takeaways
- Dynamic RLS commonly relates governed entitlements to analytical data and filters with the authenticated Tableau identity.
- Priority 1 is highest and priority 100 lowest; priority affects queue selection but does not guarantee completion time.
- Extract refresh tasks are suspended after five consecutive failures by default, and Tableau Server administrators can configure the threshold.
- Subscriptions deliver recurring snapshots, while data-driven alerts evaluate conditions on supported continuous numeric axes.
- Custom views save an interaction state without copying or changing the underlying workbook.
12.2 Row-Level Security, Schedules, Subscriptions & Alerts
Publishing a view does not mean every viewer should see every row. Row-level security (RLS) restricts records according to the authenticated user. Operational features then keep extracts current and deliver views or notifications at the right time.
Static user filters
An author can create a user filter that maps Tableau users or groups to allowed members of a dimension. This can be practical for a small and stable population. The weakness is maintenance: staffing changes and new dimension members may require the mapping to be edited and content to be republished. Test with actual users because an administrator's unrestricted view can conceal a faulty mapping.
Dynamic row-level security
A scalable pattern stores entitlements in governed data. An entitlement table might contain Username and TerritoryKey, with one row for each allowed territory. Relate or join it to the analytical data on TerritoryKey, then apply a data source filter such as USERNAME() = [Username]. ISMEMBEROF can implement carefully governed group exceptions. Because entitlements are data, authorized administrators can update assignments without editing every workbook.
The relationship design must preserve correct grain. A physical join can duplicate fact rows when one person has multiple entitlements or when multiple people share a territory. Relationships can preserve table grains, while a database-native security policy or Tableau virtual connection can centralize security further when the environment supports it. Whichever model is used, test an ordinary user, a manager, an unauthorized user, null keys, changed assignments, and extract refresh behavior.
USERNAME returns the signed-in Tableau identity. Entitlement values must use the same format and case behavior expected by the environment. FULLNAME is a display name and is generally less stable as a security key. Do not embed individual passwords as an RLS strategy.
Extract schedules and priority
Published extracts become stale until refreshed. A full refresh rebuilds the extract. An incremental refresh processes qualifying new or replacement-range records according to its key configuration, so the design must account for historical changes and deletions.
On Tableau Server, schedules and tasks are administered for background processing. Priority values run from 1 through 100, with 1 the highest priority. Priority influences which pending task is selected first; it does not guarantee an exact completion time because duration, concurrency, failures, and available Backgrounder capacity still matter.
Tableau suspends an extract refresh task after repeated failures—five consecutive failures by default. On Tableau Server, administrators can configure the threshold. Resolve credentials, network access, schema changes, or resource limits before resuming the task. Monitor the latest successful refresh rather than assuming a schedule proves freshness.
Subscriptions
A subscription delivers an image or PDF snapshot and link for a view or workbook on a configured schedule, subject to site settings and permissions. Where available, delivery after data refresh can prevent a subscription from sending before its extract is updated. The recipient sees content according to their access and the subscription's supported execution context. Use subscriptions for recurring delivery, not for conditional threshold detection.
Data-driven alerts
A data-driven alert monitors a supported continuous numeric axis in a published view and notifies recipients when the configured condition is met. If the alert command is unavailable, verify that the view has a continuous numeric axis, alerts are enabled, the user has access, and the data can be refreshed. A text table composed only of discrete headers does not supply the required axis.
An alert answers whether a measure crossed a condition. It is not a data quality warning, permission rule, or substitute for a subscription. Use a dashboard subscription for a weekly snapshot and an alert for a threshold such as inventory below a limit.
Custom views
Custom views save a viewer's filter, sort, selection, and zoom state for an existing view. A user can make a custom view the default and may share it when permitted. The custom view does not copy the workbook or change its underlying data. It is useful when a regional manager repeatedly opens the same governed dashboard filtered to a particular business unit.
Operational decision table
| Requirement | Feature |
|---|---|
| Restrict rows by signed-in identity | Dynamic RLS with entitlements or another governed security model |
| Rebuild or incrementally update a .hyper snapshot | Extract refresh task |
| Deliver a recurring view snapshot | Subscription |
| Notify when a measure meets a condition | Data-driven alert |
| Reopen a preferred filter and sort state | Custom view |
| Warn consumers that data is stale or under maintenance | Data quality warning |
Verification checklist
- Use groups and governed entitlements rather than hardcoded per-user logic where scale requires it.
- Validate row counts and totals for several identities, including a user with no entitlement.
- Confirm the published credential and network path can support unattended refresh.
- Choose full or incremental refresh based on how inserts, updates, and deletions must be captured.
- Assign priority according to business importance without promising an exact finish time.
- Monitor failure notifications and the last successful run.
- Test subscriptions, alerts, and custom views as representative recipients.
Security and operations must be verified together. A perfectly filtered workbook with a stale extract can still lead to a wrong decision, while a current extract with faulty entitlements can expose protected data.
An enterprise deployment requires row-level security across 4,000 sales representatives located in 50 distinct global sales territories. Each representative must only see transaction records corresponding to their assigned territory, while regional managers must see all territories in their region. The security model must update automatically as sales representatives change territories or leave the company, without requiring analysts to edit workbooks or republish extracts. What is the most scalable, high-performance architectural design?
A Tableau Server administrator manages an overnight extract refresh schedule where multiple large business extracts compete for Backgrounder process capacity. The administrator has an urgent executive revenue dashboard extract that must complete by 6:00 AM, alongside several non-critical historical archiving extracts. How should the administrator configure the schedule priorities, and what occurs if an extract job fails repeatedly?
A manager needs a weekly dashboard snapshot and a separate notification only when return rate exceeds 8%. Which two Tableau features match these needs?
You've completed this section
Continue exploring other exams