Skip to content

Clarify/write docs for assigning a group as Project Leader (permissions) #1067

Open

Description

@RumblingHacked

Summary

A one line description of the request. Skip this if the title is already a good summary.

Request Type

If you know, say which of these types your request is in the title, and follow the suggestions for that type when writing your description.

Type 1: support a REST API:
If it is functionality that already exists in the REST API, example API calls are the clearest way to explain your request.

Type 2: add a REST API and support it in tsc.
If it is functionality that can be achieved somehow on Tableau Server but not through the REST API, describe the current way to do it. (e.g: functionality that is available in the Web UI, or by using the Hyper API). For UI, screenshots can be helpful.
Currently, "Project Leaders" can be assigned through the Web UI but do not see anything in the API or TSC where this could be assigned through there. Attached is a screenshot of how it is currently done.
setprojectleader

Type 3: new functionality
Requests for totally new functionality will generally be passed to the relevant dev team, but we probably can't give any useful estimate of how or when it might be implemented. If it is a feature that is 'about' the API or programmable access, here might be the best place to suggest it, but generally feature requests will be more visible in the Tableau Community Ideas forum and should go there instead.

Description

A clear and concise description of what the feature request is. If you think that the value of this feature might not be obvious, include information like how often it is needed, amount of work saved, etc. If your feature request is related to a file or server in a specific state, describe the starting state when the feature can be used, and the end state after using it. If it involves modifying files, an example file may be helpful.
This feature would have it so that this process can be automated through our pipeline and would save the time of having to go in and set it manually.

Activity

  1. jorwoods commented on Jul 16, 2022

    @jorwoods
    Contributor

    Can you not do this already? I think it is already supported.

    project = server.projects.filter(name=“Test_PO209_V1.1”)[0]
    server.projects.populate_permissions(project)
    group = server.groups.filter(name=“Leaders”)[0]
    
    leader_rule = TSC.PermissionRule(group.to_reference(), capabilities={
        TSC.Permission.Capability.ProjectLeader: TSC.Permission.Mode.Allow
    })
    project.permissions.append(leader_rule)
    
    server.projects.update_permissions(project, project.permissions)
  2. RumblingHacked commented on Jul 18, 2022

    @RumblingHacked
    Author

    Thank you, this worked. I went back to check the documentation for TSC and still was not able to find reference on how to do this, would you know where in the docs it would be?

  3. jorwoods commented on Jul 18, 2022

    @jorwoods
    Contributor

    Seems editing permissions is missing from the docs. I knew how to do that from personal experience using the library.

  4. bcantoni commented on Jul 19, 2022

    @bcantoni
    Contributor

    Let's reopen this one and repurpose to improve the docs in that area.

  5. changed the title [-]Feature: Functionality for assigning a group as Project Leader[/-] [+]Clarify/write docs for assigning a group as Project Leader (permissions)[/+] on Jul 19, 2022
  6. kramantab commented on Jan 26, 2023

    @kramantab
    Contributor

    @bcantoni , @jacalata - Do you think this should be documented in the Projects category or in the permissions category? In the REST API docs, this is documented under the permissions methods, so I am thinking that we should do the same for TSC for alignment. we have yet to document the permissions category, but if this belongs there, this would be part of that effort. Let me know what you think.

  7. jacalata commented on Jan 26, 2023

    @jacalata
    Contributor

    permissions sounds right to me.

  8. github-actions commented on Aug 6, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.

  9. added
    in-progressIssues that are in-progress of being fixed
    and removed on Aug 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

docsin-progressIssues that are in-progress of being fixed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions