> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/members-teams-and-roles/roles.md). # Roles ### Choosing roles Assign roles based on what the person needs to manage or create.
RoleResponsibility
Connections ManagerManage data platform connections
Schema ManagerBuild and operate WriteBack Extreme solutions
Semantic ManagerPrepare governed datasources
User ManagerManage customer users and groups
AI ManagerConfigure AI, agents, and MCP
Analytics ViewerView dashboards
Analytics CreatorCreate and publish dashboards
Vizzy Studio CreatorBuild custom visualization extensions
Extensions ManagerMaintain installed extensions
AdministratorAdminister the entire platform
{% hint style="warning" %} Assign the minimum roles required for a person's responsibilities. Roles are additive, so a person who works across multiple areas can be assigned multiple roles. {% endhint %} ### Connections Manager Use **Connections Manager** for people responsible for connecting UAW to customer data platforms. They can: * Create, test, update, and remove data connections * Control which groups can use a connection, selected from groups they are assigned to. * Complete connection OAuth flows * Manage semantic providers, including Tableau connected apps * View connections available to their groups This role does **not** allow a person to create semantic models, manage write-back schemas, or administer users. ### Schema Manager Use **Schema Manager** for people who design and operate **WriteBack Extreme** solutions. They can: * Create and maintain write-back schemas and fields * Configure schema permissions and row-level security * Inspect and synchronize schema detection * Manage write-back workflows and workflow relations * Review and export schema audit information * Configure audit synchronization * Use connections available to their groups while building schemas ### Semantic Manager Use **Semantic Manager** for people who prepare governed data for analytics and insights. They can: * Create, update, test, and remove datasources * Inspect available connection metadata and columns * Use supported semantic-provider features to discover or synchronize source data * View connections and datasources available to their groups This role does **not** allow a person to create or maintain database connections, administer users, or create dashboards. ### User Manager Use **User Manager** for delegated customer identity and access administration. They can: * Create, update, block, remove, and export non-administrator users * Assign roles * Manage groups and group membership * Configure and run Tableau user synchronization * Configure and run Tableau group synchronization {% hint style="warning" %} User Managers cannot grant, modify, or remove administrator access. Their management scope is limited to their own groups, and the universal `Everyone` group remains administrator-only. {% endhint %} ### AI Manager Use **AI Manager** for people who operate the customer's AI capabilities. They can: * Configure and test AI providers * Select default AI configurations * Create and maintain AI agents and versions * Test and run agents * Manage AI traces * Configure MCP settings and servers * Manage assistant use-case overrides * Manage guided workflows * View available roles when configuring AI access ### Analytics Viewer Use **Analytics Viewer** for people who need to consume dashboards without changing them. They can: * Browse accessible dashboards * Open dashboard revisions * Mark dashboards as favourites * View dashboard thumbnails Dashboard visibility continues to follow sharing and other resource-level permissions. Analytics Viewers cannot create, edit, restore, delete, or share dashboards. ### Analytics Creator Use **Analytics Creator** for dashboard authors and publishers. They can do everything an **Analytics Viewer** can, plus: * Create, edit, restore and delete dashboards * Manage dashboard revisions and thumbnails * Create, update, and remove dashboard shares * Search for users when configuring dashboard sharing ### Vizzy Studio Creator Use **Vizzy Studio Creator** for people who build customer-facing visualization extensions with Vizzy Studio. They can: * Create, update, and delete extension apps * Build and preview, publish and unpublish extensions * Scan available apps * Manage revisions and rollbacks * Compare revisions * Refresh preview images * Manage the extension script allowlist * Use the related Vizzy AI workspace Publishing an extension **does not bypass the extension's own data, licensing, or deployment requirements.** ### Extensions Manager Use **Extensions Manager** for people who maintain the customer's installed extensions without authoring custom extension apps. They can: * Browse the installed-extension overview * Synchronize extensions with the Apps for Tableau catalog * Download and install extension versions * Enable or disable installed extensions * Maintain the script allowlist used by generated visualization extensions --- # 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://docs.infotopics.com/trulyp/members-teams-and-roles/roles.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.