---
schema_version: "1"
id: 3bfb32979ff305a6da9b9e5f430f081bfaf6e032c1d68bcbca39522ca681b2a6
title: User Functions
collection: tableau
version: current
locale: en-us
portal_url: https://docs.salesforce.com/tableau/current/en-us/public/desktop/functions_functions_user.md
canonical_url: https://help.tableau.com/current/public/desktop/en-us/functions_functions_user.htm
source_site: help.tableau.com
content_type: documentation
content_hash: c5d56fad5f8816f32ee2fd61139e4e8ec0464bd1ba137099436faae8dd761fb4
description: Reference for user functions used to build user filters and row-level security.
---
[Skip to main content](#main-content)

# User Functions

This article introduces user functions and their uses in Tableau. It also demonstrates how to create a user calculation using an example.

## Why use user functions

User functions can be used to create user filters or row-level security filters that affect visualizations published to Tableau Server or Tableau Cloud, so that only certain people can see your visualization.

For example, if you have a visualization that shows the sales performance for each employee in your department published on Tableau Server or Tableau Cloud, you might want to only allow employees to see their own sales numbers when they access that visualization.

In this case, you can use the ISMEMBEROF function to create a field that returns true if the username of the person signed in to the server is a member of a specified group (on the server), such as the "Managers" group, for example. Then when you filter the view using this calculated field, only a person who is part of that group can see the data.

The calculation in this case might look something like the following:

ISMEMBEROF('Managers')

Note: If your group or user names contain certain non-alphanumeric characters, you must use HTML URL encoding for the special characters when using the functions.

Some special characters are permitted without HTML URL encoding, such as underscores, parentheses, and exclamation points. `_ ( ) !` Many other characters must be encoded.

For example, the function `ISMEMBEROF("USERS+")` needs to be written as `ISMEMBEROF("USERS%2B")`, because the '%2B' is the HTML URL Encoding for the '+' symbol. For information on HTML URL encoding, please see [HTML URL Encoding Reference](https://www.w3schools.com/tags/ref_urlencode.asp) at the W3schools Web Developer site.

### User attribute functions to control and customize data access

Among the user functions in Tableau, a subset of functions called user attribute functions, can be used to hide or show data based on who's accessing the content. For the user attribute functions capability to work, user attributes must be passed to Tableau at runtime as part of the authentication workflow.

Considerations when authoring:

- User attribute functions can be included in content authored in Tableau Desktop, Tableau Cloud, or Tableau Server.
- User attribute functions in content accessed through OIDC or SAML single sign-on (SSO) workflows are supported on Tableau Cloud and Tableau Server.
- Preview of the content with these functions isn’t available when authoring in Tableau Desktop, Tableau Cloud, or Tableau Server. User attribute functions will return NULL or FALSE values. To ensure user attribute functions work as expected, we recommend you review the content after it’s made available. For more information about workflows that include these user functions, see the [Tableau Embedding API v3](https://help.tableau.com/current/api/embedding_api/en-us/docs/embedding_api_user_attributes.html) Help, Tableau Cloud [OIDC](https://help.tableau.com/current/online/en-us/openid_auth_server_config.htm#user_attributes) or [SAML](https://help.tableau.com/current/online/en-us/saml_config_site.htm#user_attributes) topics, or Tableau Server [OIDC](https://help.tableau.com/current/server/en-us/openid_auth_requirements.htm#user_attributes) or [SAML](https://help.tableau.com/current/server/en-us/config_saml.htm#user_attributes) topics.
- User attribute functions can't be used in workflows that rely on Tableau Bridge.

#### Workflow 1: Embedding workflows (JWT with Tableau connected apps or unified access tokens)

User attribute functions (USERATTRIBUTE and USERATTRIBUTEINCLUDES) in embedded content can be enabled through user attributes passed in a JSON Web Token (JWT) through:

- [Tableau connected apps](https://help.tableau.com/current/online/en-us/connected_apps.htm) on Tableau Cloud
- [Tableau connected apps](https://help.tableau.com/current/online/en-us/connected_apps.htm) on Tableau Server 2025.1 and later
- [Unified access tokens](https://help.tableau.com/current/api/cloud-manager/en-us/docs/unified_access_tokens.html) on Tableau Cloud starting from December 2025

When user attributes are passed from JWTs, embedded content authored with these functions can control and customize data displayed to users.

**Notes:**

- Check the [Tableau Embedding API v3](https://help.tableau.com/current/api/embedding_api/en-us/docs/embedding_api_user_attributes.html#known-issues) Help for _known issues_ and _limitations_ that might affect your workflow.
- For the user attribute to work:
    
    - In Tableau Cloud, the site admin must 1) enable the Control User Access in Authentication Workflows setting, 2) configure the connected app or unified access token with the user attributes claim values in the JWT, and 3) the content author must create a user attribute function (USERATTRIBUTE or USERATTRIBUTEINCLUDES).
    - In Tableau Server, the server admin must 1) enable the user attribute capability through the [Update Site](https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_site.htm#update_site) method using Tableau REST API and optionally enable the [features.VizDataServiceClientEnable](https://help.tableau.com/current/server/en-us/cli_configuration-set_tsm.htm#uaf) TSM option, 2) configure the connected app with the user attribute claim values in the JWT, and 3) the content author must create a [user attribute function](https://help.tableau.com/current/pro/desktop/en-us/functions_functions_user.htm#user_attributes).
        
        For more information, review [Customize and Control Data Access Using User Attributes](https://help.tableau.com/current/api/embedding_api/en-us/docs/embedding_api_user_attributes.html) in the Tableau Embedding API v3 Help.

#### Workflow 2: Content workflows with direct SAML or OIDC sign-in

In addition to the embedding workflow described above, user attribute functions capability is expanded to additional embedding and non-embedding workflows. User attribute functions in content can be enabled through user attributes passed in OIDC claims or SAML assertions that are captured when the user signs in to access the content if they’re configured to sign in using OIDC or SAML SSO. When attributes are passed from the claims or assertions, content authored with these functions (USERATTRIBUTE and USERATTRIBUTEINCLUDES) can control and customize data displayed to users.

**Notes:**

- See the Tableau Cloud [OIDC](https://help.tableau.com/current/online/en-us/openid_auth_server_config.htm#user_attributes_known_issues) or [SAML](https://help.tableau.com/current/online/en-us/saml_config_site.htm#user_attributes_known_issues) topics, or the Tableau Server [OIDC](https://help.tableau.com/current/server/en-us/openid_auth_requirements.htm#user_attributes) or [SAML](https://help.tableau.com/current/server/en-us/config_saml.htm#user_attributes) topics (starting with Tableau Server 2026.2) for known issues and limitations that might affect your workflow.
- For the user attribute to work, the admin must include the user attributes in the OIDC claims or SAML assertions, and the content author must create a user attribute function (USERATTRIBUTE or USERATTRIBUTEINCLUDES).

## User functions available in Tableau

### FULLNAME( )

<table class="table--plain" style="width: 100%;">
                    <colgroup><col style="width: 20%;">
                    <col>
                    </colgroup><tbody>
                        <tr>
                            <td>Syntax</td>
                            <td><code>FULLNAME( )</code>
                            </td>
                        </tr>
                        <tr>
                            <td>Output</td>
                            <td>String</td>
                        </tr>
                        <tr>
                            <td>Definition</td>
                            <td>
                                <p>	
Returns the full name for the current user. </p>
                            </td>
                        </tr>
                        <tr>
                            <td>Example</td>
                            <td><pre>FULLNAME( )</pre>
                                <p>This returns the full name of the signed in user, such as "Hamlin Myrer".</p><pre xml:space="preserve">[Manager] = FULLNAME( )</pre>
                                <p>If manager "Hamlin Myrer" is signed in, this example returns TRUE only if the Manager field in the view contains "Hamlin Myrer". </p>
                            </td>
                        </tr>
                        <tr>
                            <td>Notes</td>
                            <td>
                                <p>This function checks:</p>
                                <ul>
                                    <li><span class="mc-variable Variables.TabsProductOnline variable">Tableau Cloud</span> and <span class="mc-variable Variables.TabsProductServer variable">Tableau Server</span>:&nbsp;the full name of the signed-in user</li>
                                    <li><span class="mc-variable Variables.TabsProductDesktop variable">Tableau Desktop</span>: the local or network full name for the user</li>
                                </ul>
                                <p><b>User filters</b>
                                </p>
                                <p>When used as a filter, a calculated field such as <code>[Username field] = FULLNAME( )</code> can be used to create a user filter that only shows data that is relevant to the person signed in to the server.</p>
                            </td>
                        </tr>
                    </tbody>
                </table>

### ISFULLNAME

<table class="table--plain" style="width: 100%;">
                    <colgroup><col style="width: 20%;">
                    <col>
                    </colgroup><tbody>
                        <tr>
                            <td>Syntax</td>
                            <td><code>ISFULLNAME("User Full Name")</code>
                            </td>
                        </tr>
                        <tr>
                            <td>Output</td>
                            <td>Boolean</td>
                        </tr>
                        <tr>
                            <td>Definition</td>
                            <td>
                                <p>Returns <code>TRUE</code> if the current user's full name matches the specified full name or <code>FALSE</code> if it does not match.</p>
                            </td>
                        </tr>
                        <tr>
                            <td>Example</td>
                            <td><pre>ISFULLNAME("Hamlin Myrer")</pre>
                            </td>
                        </tr>
                        <tr>
                            <td>Notes</td>
                            <td>
                                <p>The <code>&lt;"User Full Name"&gt;</code> argument must be a literal string, not a field. </p>
                                <p>This function checks:</p>
                                <ul>
                                    <li><span class="mc-variable Variables.TabsProductOnline variable">Tableau Cloud</span> and <span class="mc-variable Variables.TabsProductServer variable">Tableau Server</span>:&nbsp;the full name of the signed-in user</li>
                                    <li><span class="mc-variable Variables.TabsProductDesktop variable">Tableau Desktop</span>: the local or network full name for the user</li>
                                </ul>
                            </td>
                        </tr>
                    </tbody>
                </table>

### ISMEMBEROF

<table class="table--plain" style="width: 100%;">
                    <colgroup><col style="width: 20%;">
                    <col>
                    </colgroup><tbody>
                        <tr>
                            <td>Syntax</td>
                            <td><code>ISMEMBEROF("Group Name")</code>
                            </td>
                        </tr>
                        <tr>
                            <td>Output</td>
                            <td>Boolean or null</td>
                        </tr>
                        <tr>
                            <td>Definition</td>
                            <td>
                                <p>Returns <code>TRUE</code> if the person currently using Tableau is a member of a group that matches the given string, <code>FALSE</code> if they're not a member, and <code>NULL</code> if they're not signed in. </p>
                            </td>
                        </tr>
                        <tr>
                            <td>Example</td>
                            <td><pre>ISMEMBEROF('Superstars')</pre><pre>ISMEMBEROF('domain.lan\Sales')</pre>
                            </td>
                        </tr>
                        <tr>
                            <td>Notes</td>
                            <td>
                                <p>The <code>&lt;"Group Full Name"&gt;</code> argument must be a literal string, not a field. </p>
                                <p>If the user is signed in to <span class="mc-variable Variables.TabsProductOnline variable">Tableau Cloud</span> or <span class="mc-variable Variables.TabsProductServer variable">Tableau Server</span>, group membership is determined by Tableau groups. The function will return TRUE if the given string is "All Users" </p>
                                <p>The <code>ISMEMBEROF( )</code> function will also accept Active Directory domains. The Active Directory domain must be declared in the calculation with the group name.</p>
                                <p>If a change is made to a user's group membership, the change in the data that is based on the group membership is reflected in a workbook or view with a new session. The existing session will reflect stale data.</p>
                            </td>
                        </tr>
                    </tbody>
                </table>

### ISUSERNAME

<table class="table--plain" style="width: 100%;">
                    <colgroup><col style="width: 20%;">
                    <col>
                    </colgroup><tbody>
                        <tr>
                            <td>Syntax</td>
                            <td><code>ISUSERNAME("username")</code>
                            </td>
                        </tr>
                        <tr>
                            <td>Output</td>
                            <td>Boolean</td>
                        </tr>
                        <tr>
                            <td>Definition</td>
                            <td>Returns <code>TRUE</code> if the current user's username matches the specified username or <code>FALSE</code> if it does not match.</td>
                        </tr>
                        <tr>
                            <td>Example</td>
                            <td><pre xml:space="preserve">ISUSERNAME("hmyrer")</pre>
                            </td>
                        </tr>
                        <tr>
                            <td>Notes</td>
                            <td>
                                <p>The <code>&lt;"username"&gt;</code> argument must be a literal string, not a field. </p>
                                <p>This function checks:</p>
                                <ul>
                                    <li><span class="mc-variable Variables.TabsProductOnline variable">Tableau Cloud</span> and <span class="mc-variable Variables.TabsProductServer variable">Tableau Server</span>:&nbsp;the username of the signed-in user</li>
                                    <li><span class="mc-variable Variables.TabsProductDesktop variable">Tableau Desktop</span>: the local or network username for the user</li>
                                </ul>
                            </td>
                        </tr>
                    </tbody>
                </table>

### USERDOMAIN( )

<table class="table--plain" style="width: 100%;">
                    <colgroup><col style="width: 20%;">
                    <col>
                    </colgroup><tbody>
                        <tr>
                            <td>Syntax</td>
                            <td><code>USERDOMAIN(&nbsp;)</code>
                            </td>
                        </tr>
                        <tr>
                            <td>Output</td>
                            <td>String</td>
                        </tr>
                        <tr>
                            <td>Definition</td>
                            <td>Returns the domain for the current user .</td>
                        </tr>
                        <tr>
                            <td>Notes</td>
                            <td>
                                <p>This function checks:</p>
                                <ul>
                                    <li><span class="mc-variable Variables.TabsProductOnline variable">Tableau Cloud</span> and <span class="mc-variable Variables.TabsProductServer variable">Tableau Server</span>:&nbsp;the user domain of the signed-in user</li>
                                    <li><span class="mc-variable Variables.TabsProductDesktop variable">Tableau Desktop</span>: the local domain if the user is on a domain</li>
                                </ul>
                            </td>
                        </tr>
                    </tbody>
                </table>

### USERNAME( )

<table class="table--plain" style="width: 100%;">
                    <colgroup><col style="width: 20%;">
                    <col>
                    </colgroup><tbody>
                        <tr>
                            <td>Syntax</td>
                            <td><code>USERNAME( )</code>
                            </td>
                        </tr>
                        <tr>
                            <td>Output</td>
                            <td>String</td>
                        </tr>
                        <tr>
                            <td>Definition</td>
                            <td>Returns the username for the current user.</td>
                        </tr>
                        <tr>
                            <td>Example</td>
                            <td><pre xml:space="preserve">USERNAME( )</pre>
                                <p>This returns the username of the signed in user, such as "hmyrer".</p><pre xml:space="preserve">[Manager] = USERNAME( )</pre>
                                <p>If manager "hmyrer" is signed in, this example returns TRUE only if the Manager field in the view contains "hmyrer". </p>
                            </td>
                        </tr>
                        <tr>
                            <td>Notes</td>
                            <td>
                                <p>This function checks:</p>
                                <ul>
                                    <li><span class="mc-variable Variables.TabsProductOnline variable">Tableau Cloud</span> and <span class="mc-variable Variables.TabsProductServer variable">Tableau Server</span>:&nbsp;the username of the signed-in user</li>
                                    <li><span class="mc-variable Variables.TabsProductDesktop variable">Tableau Desktop</span>: the local or network username for the user</li>
                                </ul>
                                <p><b>User filters</b>
                                </p>
                                <p>When used as a filter, a calculated field such as <code>[Username field] = USERNAME( )</code> can be used to create a user filter that only shows data that is relevant to the person signed in to the server.</p>
                            </td>
                        </tr>
                    </tbody>
                </table>

### USERATTRIBUTE

<table class="table--plain" style="width: 100%;">
                    <colgroup><col style="width: 20%;">
                    <col>
                    </colgroup><tbody>
                        <tr>
                            <td>Syntax</td>
                            <td><code>USERATTRIBUTE('attribute_name')</code>
                            </td>
                        </tr>
                        <tr>
                            <td>Output</td>
                            <td>String or null</td>
                        </tr>
                        <tr>
                            <td>Definition</td>
                            <td>
                                <p>If <code>&lt;'attribute_name'&gt;</code> is part of the JWT (via connected apps, UAT, OIDC claim) or SAML&nbsp;XML&nbsp;response passed to Tableau, the calculation returns the first value of <code>&lt;'attribute_name'&gt;</code>. </p>
                                <p>Returns null if <code>&lt;'attribute_name'&gt;</code> does not exist.</p>
                            </td>
                        </tr>
                        <tr>
                            <td>Example</td>
                            <td>
                                <p>Suppose "Region" is the user attribute  included in the JWT or SAML&nbsp;response and passed to Tableau.</p>
                                <p> As the workbook author, you can set up your visualization to filter data based on a specified region. In that filter, you can reference the following calculation.</p><pre xml:space="preserve">[Region] = USERATTRIBUTE("Region")</pre>
                                <p>When User2 from the West region views the embedded visualization, Tableau shows the appropriate data for the West region only.</p>
                            </td>
                        </tr>
                        <tr>
                            <td>Notes</td>
                            <td>You can use the <code>USERATTRIBUTEINCLUDES</code> function if you expect <code>&lt;'attribute_name'&gt;</code> to return multiple values.</td>
                        </tr>
                    </tbody>
                </table>

### USERATTRIBUTEINCLUDES

<table class="table--plain" style="width: 100%;">
                    <colgroup><col style="width: 20%;">
                    <col>
                    </colgroup><tbody>
                        <tr>
                            <td>Syntax</td>
                            <td><code>USERATTRIBUTEINCLUDES('attribute_name', 'expected_value')</code>
                            </td>
                        </tr>
                        <tr>
                            <td>Output</td>
                            <td>Boolean</td>
                        </tr>
                        <tr>
                            <td>Definition</td>
                            <td>
                                <p>Returns <code>TRUE</code> if both of the following are true:</p>
                                <ul>
                                    <li><code>&lt;'attribute_name'&gt;</code> is part of the  JWT (via connected app, UAT, OIDC claim) or SAML&nbsp;XML&nbsp;response passed to Tableau</li>
                                    <li>one of <code>&lt;'attribute_name'&gt;</code> values equals <code>&lt;'expected_value'&gt;</code> . </li>
                                </ul>
                                <p>Returns <code>FALSE</code> otherwise.</p>
                            </td>
                        </tr>
                        <tr>
                            <td>Example</td>
                            <td>
                                <p>Suppose "Region" is the user attribute  included in the JWT or SAML response&nbsp;and passed to Tableau.</p>
                                <p> As the workbook author, you can set up your visualization to filter data based on a specified region. In that filter, you can reference the following calculation.</p><pre xml:space="preserve">USERATTRIBUTEINCLUDES('Region', [Region])</pre>
                                <p>If User2 from the West region accesses the embedded visualization, Tableau checks if the Region user attribute matches one of [Region] field values. When true, the visualization shows the appropriate data. </p>
                                <p>When User3 from the North region accesses the same visualization, she’s unable to see any data because there’s no match with [Region] field values.</p>
                            </td>
                        </tr>
                    </tbody>
                </table>

## Create a user calculation

User calculations work directly with the users and groups you have set up on Tableau Server or Tableau Cloud. You can create user calculations to use as filters so users only see the data that is relevant to them.

For example, if you have a map viz similar to the following, which shows sales data for 48 US states, you can create a user calculation to show only parts of the map that are relevant to each user, such as data relevant for a regional manager versus a national manager. (A national manager should be able to see data for the entire country, while a regional manager should only be able to see data for the region they manage).

When the national manger is signed in, they see the following visualization:

![A filled map of the United States shows total sales by region.](/tableau/current/en-us/public/desktop/en-us/Img/userfunctions1.png)

When the western regional manager is signed in, they see only sales for their region:

![A color-coded map of the western United States, with California standing out for the highest sales volume.](/tableau/current/en-us/public/desktop/en-us/Img/userfunctions2.png)

To create a user function that performs similarly to this example, follow the steps below.

### Before you begin

To follow along with this example you must have access to Tableau Server or Tableau Cloud. You must also be a Server or Site Administrator.

### Step 1: Create the users and groups

1. Sign in to Tableau Server or Tableau Cloud.
2. In Tableau Server or Tableau Cloud, add the following users:
    
    - Sadie Pawthorne
    - Chuck Magee
    - Fred Suzuki
    - Roxanne Rodriguez
    
    For more information, see [Add Users to a Site](http://onlinehelp.tableau.com/current/server/en-us/sites_addusers.htm) in the Tableau Server Help.
3. Create a new group called **National Managers**.
    
    For more information, see [Create a Local Group](http://onlinehelp.tableau.com/current/server/en-us/groups_create_local.htm) in the Tableau Server Help.
4. Add yourself to the National Managers group.
    
    For more information, see [Add Users to a Group](http://onlinehelp.tableau.com/current/server/en-us/users_add_group.htm) in the Tableau Server Help.

### Step 2: Create the visualization

1. Open Tableau Desktop, and connect to the **Sample-Superstore** data source, which comes with Tableau.
2. In the bottom left corner of the workspace, click the Data Source tab.
3. On the Data Source page, from the Connections pane on the left, drag the People sheet to the join area.
4. Click the join icon and select Left.
    
    ![Create a left join.](/tableau/current/en-us/public/desktop/en-us/Img/user_functions1.gif)
5. Navigate to a new worksheet.
6. In the **Data** pane, under Dimensions, double-click State.
    
    A map view is created.
7. From the **Data** pane, under Measures, drag Sales to Color on the Marks card.
8. On the Columns shelf, select the Longitude field and hold down Control (Comman on Mac) on your keyboard to copy it. Drag the copy to the right of the original on the Columns shelf.
    
    ![Create a dual axis map in Tableau.](/tableau/current/en-us/public/desktop/en-us/Img/user_functions2.gif)
9. On the Marks card, click the second (bottom) **Longitude** tab.
10. From the **Data** pane, drag Region to Color on the Marks card.
    
    The map view on the right updates with new colors.
    
    ![A map view with the new color palette applied.](/tableau/current/en-us/public/desktop/en-us/Img/user_functions3.png)
11. On the Marks card, click the mark type drop-down and select **Map**.
    
    ![The Marks card with Map selected.](/tableau/current/en-us/public/desktop/en-us/Img/user_functions4.png)
12. On the Marks card, click **Color**, and, under Opacity, adjust the slider to 50%.
13. On the Marks card, click the first **Longitude** tab.
14. On the Marks card, click Color \> Edit Colors, and then select **Gray** from the color palette drop-down list.
    
    The map view on the left updates.
    
    ![A map view with the new color palette applied.](/tableau/current/en-us/public/desktop/en-us/Img/user_functions5.png)
15. On the Columns shelf, right-click the **Longitude** field on the right and select Dual Axis.
    
    ![The Columns menu with Dual Axis selected.](/tableau/current/en-us/public/desktop/en-us/Img/user_functions7.png)

The map looks like the following:

![A map view with the new columns applied.](/tableau/current/en-us/public/desktop/en-us/Img/user_functions6.png)

### Step 3: Create the User Calculation

1. Select Analysis \> Create Calculated Field.
2. In the calculation editor that opens, do the following:

- Name the calculated field, User Filter.
- Enter the following formula:
    
    `[Regional Manager] = USERNAME() OR ISMEMBEROF("National Managers")`
    
    This calculation checks if a person is included in the Region (People) field, or if a person is included in the National Managers group. If so, it returns true.
- When finished, click OK.

The new user calculation appears under Dimensions in the Data pane. Just like your other fields, you can use it in one or more visualizations.

### Step 4: Add the user calculation to the Filters shelf

1. From the Data pane, under Dimensions, drag User Filter to the Filters shelf.
2. In the Filter dialog box that opens, select True, and then click OK.

### Step 5: Test the calculation

1. In Tableau Desktop, in the bottom-right corner of the workspace, click the Filter as User drop-down and change the user to Sadie Pawthorne.
    
    The map updates to show only the West region of the United States because Sadie is assigned to the West region in the People sheet.
2. Select the Filter as User drop-down again and change the user to Roxanne Rodriguez.
    
    The map updates to show only the Central region of the United States because Roxanne is assigned to the Central region in the People sheet.
3. Select the Filter as User drop-down again and change the user to Chuck Magee.
    
    The map updates to show only the East region of the United States because Chuck is assigned to the East region in the People sheet.
4. Select the Filter as User drop-down again and change the user to Fred Suzuki.
    
    The map updates to show only the South region of the United States because Fred is assigned to the South region in the People sheet.
5. Select the Filter as User drop-down one more time and change the user back to yourself.
    
    The map updates to show all data because you are a part of the National Managers group on the server.

This behavior persists when you publish the view to Tableau Server or Tableau Cloud. Users not listed in the National Managers group, or in the People sheet in the Sample Superstore data source see only a blank visualization.

## See Also

[Functions in Tableau](https://help.tableau.com/current/public/desktop/en-us/functions.htm)

[Tableau Functions (by Category)](https://help.tableau.com/current/public/desktop/en-us/functions_all_categories.htm)

[Tableau Functions (Alphabetical)](https://help.tableau.com/current/public/desktop/en-us/functions_all_alphabetical.htm)