Admin Best Practices

Your trial environment has been converted into a production environment. All users, groups, and datasets that were created during your trial carried over. You can access your production environment in the same way as you did with the trial environment.

You can skip to the second step below.

You will have to get started with no users, groups, or personalized datasets created in the environment. As an org admin, getting others access to the platform is critical.

Follow the steps below starting with the first step.

As an org admin, you should have received a confirmation email from the Alteryx Fulfilment team that your organization has been set up (see screenshot). Within the email, there is a link for you to sign in to AAI. If you have not received a confirmation email, please submit a support ticket. To do so, sign in to the community and go to Submit A Case. Our support engineering team is ready to help.

Sign in to AAI to check that your organization has been set up correctly.

For customers running Auto Insights SaaS on Microsoft Azure, use the link that corresponds with where your environment was set up (US, UK, EU, SG, AU) and your email/password. Replace REGION with the correct 2-letter region and access the URL: https://REGION.autoinsights.alteryxcloud.com/

Once you have signed in, check that you have Admin portal access. To do so, select your profile icon (top right of your screen).

Next, go into the Admin portal and check that your organization is correct (top right of your screen).

If any of those checks fail, sign in to Alteryx Community and Submit A Case to our support engineering team. They are ready to help.

Identify a group of users that you want to be admins and create their AAI user profiles. While you might think of setting aside some licenses for future users, it is best practice to use all licenses within the first month. This ensures that those users are part of any initial enablement and communication. You can always redistribute licenses in the future.

You can refer to this article on inviting new users. We recommend using individual user creation at the start. For Creators, you will want to set their role as ‘Administrator’ (Viewers should be set as ‘User’). Learn more in the Rolesarticle.

Here’s a flow guide you can refer to for subsequent management of users.

Introducing AAI to your admin group. Now that you've created admin profiles in AAI, send an introduction email to the creator group.

Refer to this best practices article on productionizing your first use case.

For every dataset that an admin loads, AAI automatically creates an ADMIN group with that admin as a member. For example, John Doe (Creator) loads a dataset and names it ‘Sales POS transaction’, AAI creates a ‘Sales POS transaction_ADMIN’ group, and John Doe is automatically added as a member. Below are best practices for the maintenance of Admin and Viewer communities.

For scenarios where the viewer community needs to maintain an ethical wall (have restricted data access), you should implement groups as well as row-based permissions to provide that security.

Note that pending profile links are generated for 7 days. We recommend following up with the users to ensure that they have logged in, or else the pending profile will be deleted on the 7th day.

We recommend you review user access quarterly.

We recommend reviewing the dataset list in AAI every quarter to remove test datasets that are no longer relevant. This ensures the datasets and groups in AAI remain relevant for your organization, which can make assigning dataset access to users less overwhelming.