This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Accounts for your Connect instance can be created in multiple ways:
• Allowing users to “Sign Up”
o Email address domain must be in “Allowed Domains” o Works with Manual, AD, and SAML authentication, though the interfaces are slightly different o Manual Sign-Up may be disabled with the checkbox in Administration > Connect Configuration > Instance Settings
• An Administrator creates an account
o Not required to supply a password o Should always supply an email address
In all cases, the user account will initially be placed into the defaulted permission group.
Connect will attempt to consolidate created accounts by email address. Regardless of how the account was created (manual “Sign In”, by an administrator, from the Tableau Metadata Loader, or from the Alteryx Metadata Loader), the account will consolidate if the email exists already within the system.
Note: If you have a large number of potential Connect users in Gallery or Tableau Server, it is recommended to first run the respective loader early in your setup process rather than manually creating accounts. In AD Authentication, the email address becomes the key, so the email must line up in order to not duplicate user accounts.
In Alteryx Connect, permissions can be managed individually or with Groups. By default, there are four Groups, which you can find under “People” on the homepage:
o Add/remove metadata o Access the Admin configuration panel o Can add users and permissions
o Can mark data assets as “Certified” or “Do not Use”. Should also have at least Reader permission
o The initial default Group for new users o Contributors may edit asset attributes o Allows social interaction
o Allows Viewing o Allows social interaction
Note: You may add new groups, but it is not recommended to delete default Groups.
Default User Groups
Newly-created accounts will be given a single default permission. By default, that group is “Contributors.”
To change the default: 1. Edit “Contributors” group and remove the value “defaultGroup” from the field “Integration Code”. Save after this modification:
2. Edit the Group you want to set as the default group, and add the value “defaultGroup” to the field “Integration Code”, and then click “Save”
Note: For the most secure configuration, create a new group called “NoAccess”, and set it to be the default group. If you do not grant Viewer rights to this group on the homepage, anyone in this group will default to no access, receiving this message:
Custom User Groups
An Admin can create new groups, which can then be associated with permissions:
1. Navigate to the “Groups” page within “People” 2. Click the orange plus button at bottom right to add a new group 3. Give the group a name and description 4. After saving the group, you can add existing users to the group by editing it and adding the desired user to List of Users > Members, and clicking “Save”:
Note: Users may be associated with multiple groups. By nature, the application of permissions are permissive rather than restrictive. Eg: If a user belongs to any group that has “Viewer” capability for an asset, the user will be able to view the asset.
Permissioning with Groups
Individuals or Groups may be provided with access to different permissions to interact with Connect entity pages. To make a page visible to only a particular group, follow these steps:
1. If you do not already have a custom Group defined, create one within People > Groups. Add at least one user to your Group and “Save”:
2. Navigate to a specific asset page, for example, a database table 3. As an Administrator, click the vertical ellipses icon at top right and click “Permissions”:
The table at top lists the current effective permissions per action (which are often inherited from parent pages):
Below the table you have the opportunity to modify those permissions by specifying the respective Group(s) for each permission; just enter desired Group into the correct permission category and select “Save”:
Note: Permissions impact search results in real-time and permissions are hierarchically applied. If you permission a database schema, all the tables, views, and columns within that schema will be affected.
Administrators can see and edit all permissions at any time from the administrative interface under their user icon Administration > Permission Overview: