Note: Starting in Tableau Server 9.2, you can set permissions for only these capabilities in a project: Read (view), Write (save),Īnd ProjectLeader. (The default value for this attribute is ManagedByOwner.) Update Project (Link opens in a new window) You include the contentPermissions attribute in theĬreate Project (Link opens in a new window) When it's published, and the permissions for that content cannot be changed, even by the content owner. In that case, the project default permissions are assigned to content ![]() Query Default Permissions (Link opens in a new window)ĭelete Default Permission (Link opens in a new window)Īdministrators and project leaders can also "lock" these default permissions. REST API methods to work with project default permissions:Īdd Default Permissions (Link opens in a new window) These permissions are then assigned by default to content that's published to the server. Starting in Tableau Server 9.2 (REST API version 2.1), server administrators, site administrators, and project leaders can define default Project default permissions and permissions locking ThisĮxample assigns the Allow permission to the Read and Write capabilities of the project for the user whose ID is 9f9e9d9c-8b8a-8f8e-7d7c-7b7a6f6d6e6d. The following example shows what the body of an Add Project Permissions request might look like. ![]() The documentation for an individual API (such as Add Workbook Permissions orĪdd Project Permissions) specifies the capabilities that you can pass for that API. In contrast, for a workbook, you can assign permissions for the Individual entities (project, workbook, and data source) support different capabilities. The mode for the permission, which is either Allow or Deny. Used in the server environment, as listed later in this topic.) (These reserved names correspond to names that are You specify the capability using a reserved name that's defined in the REST API XML schema, The capability that you're assigning permissions to. Grantees are identified by ID (LUID), not name. (A grantee is sometimes referred to as a principal.) The grantee, that is, the user or group that you are assigning the permission to. ![]() When you add permissions to an entity like a project, To assign appropriate permissions to the new project. You can use methods in the REST API to assign or edit permissions for projects, workbooks, and data sources. The user's implicit permissions are not listed. The term implicit is used because if you query the user's permissions, (including projects under parent projects that they own). That the user has because the user is a server administrator, or the owner of an entity.Īdministrators do not have to be explicitly granted any permissions, and owners do not have to be granted permissions for content that they own In contrast, implicit permissions are those If you query a user's permissions,Įxplicit permissions are listed in the display. "only if they have ExportXml permission for the data source (either explicitly or implicitly)."Įxplicit permissions are those that have been assigned to the user. The Download Datasource method indicates that the users can call the method Note: The documentation occasionally refers to explicit and implicit permissions. ![]() The documentation for individual methods indicates the permissions that are required in order to call that method. To perform the task that is represented by the method. Other methods can be called by any user who has been granted appropriate permissions Many methods, such as adding or removing usersįrom the server, require the user to be a server administrator. A user's set of permissions is determined by the user's identity-that is, by the credentials that the user passes when calling Sign In. Users who call REST API methods must have permission to perform the task represented by each method that they call.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |