The Shared space is the default location for Dashboards and Looks intended to be shared with an organization (or with one or more departments in an organization). For the most part, there are three levels of Dashboard and Look sharing:
- Not shared at all. If a Dashboard or Look is intended for your use only, you can store this item in your personal space and not give anyone else access to the space.
- Shared with a few people. If you want to share a Dashboard or Look with a selected group of people, you can store that item in your personal space and then give access to specific users and/or specific groups.
- Shared with everyone. If a Dashboard or Look is intended for use by your entire organization (or by an entire department), you can store that item in the Shared space. Items in the Shared Space inherit the access settings configured for the Shared space: if everyone in the organization has access to the Shared space then everyone in the organization will have access to the Dashboards and Looks found in that space. (Keep in mind, however, that only administrators have the right to store items in the Shared space.)
Of course, you don’t have to give everyone access to a Space; that’s up to you. Alternatively, you can also create sub-spaces and use different access permissions for each of those spaces. For example, you might create a sub-space named IT and give access only to users who belong to the IT group. Or suppose you access a Space and see something similar to this:
This simply means that this Space contains a pair of sub-spaces: Custom Reports and Customer Journey Analytics. If you choose, you can set different access permissions on these two spaces. Let’s assume that Custom Reports is for all users, and Customer Journey Analytics is only for users who belong to a specific group. In that case, a user who doesn’t belong to that group will see this when he or she access the Shared Space:
By default, each folder in the Shared space represents a single Identity Cloud application. For example, suppose your Shared space looks similar to this:
In this case, that means that, by default, you have three Akamaki applications corresponding to the folders @Janrain Demos, @Janrain Internal, and @Janrain Training. Keep in mind however, that a single folder can contain numerous subfolders. For example:
Keep digging, however, you’ll eventually find a single folder that houses Dashboards for a single application. That’s important to know, because Customer Insights is limited to working with one application at a time. For example, suppose you have three applications: Applications A, B, and C. You can use a Dashboard to look at user profile counts for Application A, and you can use a different Dashboard to look at user profiles counts for Application B and another for Dashboard C. But you cannot use the same Dashboard to look at the combined profile counts for Applications A, B, and C. To get that combined value, you’ll have to manually add the profile counts for each application.
Incidentally, if you end up nesting folders inside of folders inside of folders, you can use the breadcrumbs at the top of the page to back your way out of your current location: