Welcome to the Alteryx Knowledge Base

This is Part 4of the Alteryx Gallery Series -The Gallery Series only refers to the Alteryx Server where you can host your Private Alteryx Gallery. This Article with refer to 'Alteryx Gallery' as a privately hosted Gallery on the Alteryx Server.

Part 1 Alteryx Gallery Series - The Lay of the Land 101: Gallery Admin Edition
Part 2 Alteryx Gallery Series - The Lay of the Land 101: User Edition
Part 3 Alteryx Gallery Series: App Publishing & Version Control 101 - Alteryx Community

 

With the enormous potential of the Alteryx Gallery it is important to utilize all of its power into making better data driven decisions. But, what if you are unsure how to shape the Gallery for your particular use case? This article outlines a few of the potential ways you can do that.

 

Data Analyst

This is a simple way of organizing the Gallery if you have a small groups of Alteryx Content creators who develop end solutions for Business Decision Makers in certain internal departments.

• You have a few Data Artisans who create, parametrize and upload the Applications (Gallery Admin will need to assign Data Artisan level permissions for these users)
• They all have private studios to develop in to push content up (Default)
• They have the ability to create Collections for end users and invite them to join (End users will need to have signed up to the Alteryx Gallery or be in the Domain where the Alteryx Gallery is hosted)
• The owner of the collection will then have to use the ‘users’ tab inside the collection to add the end user who will then be able to run the reports as a ‘Viewer’ of the Collection.

 

Departmental (Functional)

You have a group of Alteryx creators who make custom applications for particular departments. You would like to share these applications across multiple users within that department.

• You have a few Data Artisans who create, parametrize and upload the Applications (Gallery Admin will need to assign Data Artisan level permissions for these users)
• The Gallery Admin has created a Studio (Subscription) for that particular department and given the Alteryx creators Artisan permissions to that studio. As Data Artisans can only belong to one studio at once, the application they build in the Alteryx Designer will now ‘land’ in that departmentsprivate studio. (Use this as a development platform).
• Once the application have been tested, the Gallery Admin can then assign the Data Artisans to a collection whereby they can upload the finished applications. The Gallery Admin can then add the end users to that collection to run the applications as “Viewers”

 

Departmental (Consumer)

You have multiple different departments consuming these applications from one set of Alteryx creators. The end users just want to run the application without knowing any of the Alteryx behind the scenes logistics.

• As Data Artisans can only publish to one studio (subscription) at a time, it may be useful to have a cross-functional studio to house applications for different departments.
• The Gallery Admin know can just assign one subscription/studio key to each Data Artisan.
• The Data Artisan uploads to this one cross-functional studio
• Once the applications have been uploaded to the Studio they can then be published to the end users in the specific department collections. The users have already been invited to that collection by the Gallery Admin.

 

Hierarchy (Varied End Users)

You have a range of end users requesting detailed reporting

• The Gallery Admin assigns a cross-functional studio for all Data Artisans.
• Analysts require a greater range of detail for their UI on their applications. Therefore, the Gallery Admin creates a collection for analysts and invites the Data Artisan to publish the more detailed applications here.
• Management require more cohesive and precise reporting so these application are hosted in a different collection for these users.
• All of the end users (analysts & management) are invited as viewers to just run the workflows.