Thanks for bringing this up. This is a bug--please work with Support to resolve!
Anup, I spent sometime to test your scenarios and here is my findings:
- For User A being able to publish to County A, user A has to have publisher permission not only for County A but also for Virginia, USA, and all the level to the top parent project.
- For User B being able to publish to County B, user B has to have publisher permission not only for County B but also for Virginia, USA, and all the level to the top parent project.
- If you setup above #1 and #2, User A will NOT be able to publish to County B. User B will NOT be able to publish to County A, which is what you wanted.
Pls vote for idea https://community.tableau.com/ideas/8490
Allow publisher permission to child project only w/o publisher permission at parent project
Thanks for the response Mark.
I set these permissions up and had my users test out the scenarios. Unfortunately User A has to be set up as a publisher at the top parent project all the way down to 'County'project level else they get a message that they do not have rights to publish.
If I set them up (same you mentioned), then they are able to publish to their projects and other projects too...
Correct but pls confirm User A will not be able to publish to County B although User A is able to publish all upper projects.
If your concern is User A being able to all the upper projects, the nested project does not work for you or you need to re-structure the project to flat it out with less levels.
If your concern is User A being able to publish to sister project County B, you don’t have to concern. The key feature here is User A can’t publish to County B although User A can publish its upper projects. I will design a flatter hierarchy to leverage this key feature.
Sent from my iPhone
User A was able to publish to County B. I am re-thinking the hierarchy to manage the permissions better.
Thanks for your help.
If your User A is able to publish to County B. Either it is a bug or setup is wrong. I wanted to document my setup as your reference. In my setup, User A can't publish to County B. I double verified this.
1. Nested-Project has two sub-folders: Project A and Project B
2. I have two publishers : Publisher4 and Publisher5. I have to give both publisher permission for Nested-Project.
3. I setup Publisher5 the publisher permission only for Project A
4. And setup Publisher4 the publisher permission only for Project B
5. From Desktop, Publisher5 only sees Project A, which is good.
6. From Desktop, Publisher4 only sees Project B, which is good too.
Thank you very much for the detailed notes. I have set this up for a couple of users and should be able to have them test it. The scenario you have outlined will most likely be the option we go with for now.
I would like Tableau to fix the situation where Publisher 5 and Publisher 4 can only publish to their individual projects and not to the parent project (Nested-Project).
Thanks again for your guidance. Helped clarify a lot of potential questions for our enterprise rollout of the new 10.5 server.
A question about the permissions for Publisher 4. You have set Publisher 4 as 'Publisher' on 'Nested-Project', but what about the permissions for 'Workbooks' and 'Data Sources'? Have they been defaulted to 'None'? The reason I ask is if the permissions are set to 'None' for 'Workbooks' and 'Data Sources', then Publisher 4 can navigate the hierarchy, but not publish at the 'Nested-Project' level, which is exactly what I need.
1 of 1 people found this helpful
Anup, You can't avoid to give Publisher4 or Publisher5 publisher permission at the 'Nested-Project' level. If they do not have it, they can't see sub-project folder during publishing - it means that they can't publisher to sub-folders. I do not like this either, pls vote https://community.tableau.com/ideas/8490
When you give Publisher4 or Publisher5 publisher permission at the 'Nested-Project' level, they will be able to publish to 'Nested-Project' no matter what permissions they have for 'Workbook' or 'Data Sources'.
What it means if Publisher4 has publisher permission at 'Nested-Project' and none for 'Workbook' and none for 'Data Sources'?
- Publisher4 can publisher to 'Nested-Project'
- When Publisher6 publishes to 'Nested-Project', by default, Publisher4 will get none permission for Publisher6's workbook or data sources. However Publisher6 can always give Publisher4 whatever permissions for Publisher6's workbooks or data sources during or after the publishing process
1 of 1 people found this helpful
As Mark Wu suggested. There is no way where you can set users/AD group as Publisher at sub project and not setting them as publishers at Project level.
Users have to be Publishers at Both Project & Sub Project level. The current Tableau Set up is like that.
I have gone through this cycle to discover this behavior.
Thank you very much. I have configured the permissions with an understanding of the current limitations. I have also voted up the idea...
For the below scenario we have
User Name Site Role Group
User A Publisher CountyA_Publisher
User B Publisher CountyB_Publisher
I was just wondering, why not setup the user in this fashion:
- Create Groups "North America", USA, Virginia - Set these groups to be viewers on respective folders.
- Make "User A" & "User B" member of all the groups above
- Create "CountryA_Publisher" Group
- User A will be part of "CountryA_Publisher" Group
- Create "CountryB_Publisher" Group
- User B will be part of "CountryB_Publisher" Group
I am assuming with your expertise you had realized this, but didnt that work ?
I'm excited to report that we have released this capability in our September maintenance release, going back to all major releases since 10.5 when nested projects were launched. With the update, users now have the ability to browse the project hierarchy and publish to a nested project even if the user doesn't have permission to the parent project.
In the example below, I have permission to publish in the Supplier Details but not in the Suppliers. You see that the Supplier project is greyed out and cannot be selected but can be expanded to show the nested project. Users will need to have at least View permission on the parent projects to navigate through the project tree.
To enable this capability, users will need to update Tableau Desktop and administrators will also need to update Tableau Server. Using Tableau Online? You just need to update your version of Tableau Desktop.