Hello, Hoping to get an explanation about CreateFolder API. https://docs.aws.amazon.com/quicksight/latest/APIReference/API_CreateFolder.html
I’m trying to understand what SharingModel does. I understand it can be either NAMESPACE (default) or ACCOUNT.
But when I create a shared folder with either values for SharingModel, and share with a user, how would choice of SharingModel affect the experience.
Hi @tlm234,
To my understanding, the ‘SharingModel’ handles who you are allowed to share with from that folder.
So regarding the options:
I’ve included some additional documentation below regarding namespaces:
Folder lives in an account. So what does ‘..same namespace‘ in SharingModel: NAMESPACE mean?
Hi @tlm234,
The article I included above contains additional information on namespaces and when they would best be utilized:
”Namespace: – Is a way to organize groups and users within a single AWS account, allowing different teams or departments to work with their own data and assignments, and manage access to those assets. By creating a namespace, an administrator can invite other users to join and assign them different roles and permissions. Namespaces are designed to span AWS Regions, so the containment doesn’t change even if a user signs into a different AWS Region. All namespace assets are managed by API/CLI calls.”
Sorry I’m familar with what a namespace is. Thats not my question.
Hi @tlm234,
If your folder lives in an account and you’d like the ability to grant access to the folder assets to anyone with the account, you would use the ‘ACCOUNT’ option.
If you also have a namespace setup within your account (that you or the user creating the folder is assigned to) and would only like to grant access of the folder assets to others within the namespace, you would use the ‘NAMESPACE’ option.
If your folder has been created in your account and there are no namespaces that exist (or all users in the account are also active within the namespace), using the ‘NAMESPACE’ option would have not have an affect.
But as namespaces live within an account, there may be instances where you’d like to setup a folder that is accessible to all users within an account, there may be instances where you’d only like to create a folder for that namespace, or you’d like to create a folder that is accessible to all within an account, no matter the namespace they are also attached to.
Ultimately who has access to the folder is determined by whom I give permission (user/group) as owner/contributor/viewer. I can share folder with anyone from any namespace using API.
All I’m asking is how would choice of SharingModel affect the experience.