We wish to create a custom role for a YouTrack project whose members cannot add or delete any issues but can be assigned an issue.
There are 28 distinct permissions for YouTrack that can be granted when creating a role.
Which of these get the user having this role into the assignee list for that project?
Here's the list of permissions for the predefined "Developer" role, that is meant for assignees of the issue: https://www.jetbrains.com/help/youtrack/standalone/7.0/Default-Roles.html?search=role#d26854e213 . I'd recommend to use it as a reference for the permissions' list, without including "Create issue" or "Delete issue" permissions.
Related
I have a user with permissions across many projects (see image below).
I have a new user who just joined the company. I want to give him the exact same permissions. How can I do this? I don't want to do it manually because that will take me ages and the Google Cloud Documentation is useless! I cant find much on using gcloud command line to do this with examples.
There must be a easy way to duplicate permission?
Thanks
It is indeed possible to grant a role to a member for more than one project:
Open the IAM & Admin Projects page in the GCP Console.
Select all the projects for which you want to grant permissions.
Click the Show Info Panel, followed by the Permissions tab.
Enter an email address in the Add members field, and select the desired role from the drop-down menu.
Click the Add button. The member will be granted the selected role in each of the selected projects.
Granting access rights to project is an action fraught with security risks, so bulk gcloud commands or simple copying of roles are understandably not supported.
You can find more detail on the "Granting, Changing, and Revoking Access to Resources" documentation page.
Greetings.
I am working on a Drupal 7 site and wanted to discuss few permission related things where I am facing issues.
I want the below mentioned permissions:
1) I want to create a user lets say "Job posting manager" for example. Who can only create , edit job content type. No option to publish.
2) I want to create a another user lets say "Job admin manager" for example. Who can publish / edit the job along with create job.
So how can I set this type of permission for only specific content type and specific users?
Thanks in advance.
Let's say the Content Type is named "job".
You'd need to create two Roles:
Job Posting Manager
Job Admin Manager
You can create these two roles by visiting admin/people/permissions/roles (bottom of the page)
Once the two roles are created, you should create two different users and assign them the proper role:
User1 -> Assign the role "Job Posting Manager"
User2 -> Assign the role "Job Admin Manager"
As a last step, you need to assign the proper permission to the newly created roles:
Visit: admin/people/permissions
Filter for "node" section and assign the permissions as you desire.
For a more detail workflow solution, take a look at Workbench and its submodules like Workbench Moderation.
I have to create a list with different permission levels. I can see my list, but my teammates can't, but my manager can see all list.
I tried to use filters, but I couldn't define a filter for my manager. I was able to filter the list between teammates.
Is there any way to create groups of permissions. For example, the owners can see the full list, but the members can see their own part
Access to lists or items in them is determined by permission levels. You can check permission level for particular user or group by Check permission Button on List Permission Settings page.
You should also know that there are some users that can access lists and items without explicit permission grant in list's permission list. Farm admins, Site Collection admins or users have granted access at Web application level in Central administration.
Adding permissions to a role enables the given permission to all users in that role by default; this is something I want to avoid.
I want to be able to set permissions like "Booking: View own Bookings" at user level and not the role level.
Is there a module that already does this, or can someone give me some possible approaches or pseudo code of some kind?
Yes, there's the User Permissions module.
User Permissions provides an interface for giving additional permissions to individual users without the need to assign them to a special role. When this module is enabled, users with the 'administer permissions' permission can access the 'User Permissions' tab on each user's account.
I would be happy to get some advice on "workflow" type. Im not sure what is best - "Intranet/Extranet", "Simple Publication" or a third choice. Below are the types of folders and roles Im looking for:
public folders: anonymous has "r".
intranet folders: users has "r". Special users has "rw".
private folders: only user in question and admin has "rw" (special users has also "rw")
special folder: users that are member of a group has "rw".
Lastly, I do not understand this, users with e.g. "read", "edit" or "contribute" role can see user folders (marked as private), but also a test folder created as admin (marked as private)? PS Im using "Intranet/Extranet" type.
Thanks.
Nikolaj G.
You're confusing Roles and Permissions in your question. "read" and "write" would be permissions. Reader, Editor, Contributor are Roles.
In an Internet/Extranet workflow, Anonymous users (a Role) would get Read access to Public content.
Private content would be accessible to users with the Owner or Manager (Administrator) role
"Internally Published" content is readable by users with Contributor, Editor, Manager, Member, Owner and Reader roles, but only editable by Managers.
"Internal" would correspond to the "Intranet" setting you want - where most users get read access, but you can give users the "Editor" role (using the sharing tab) to allow them to modify content.
Your "special" folders would simply be in the "Internal" state, but you would grant the Editor role to a group rather than a user.
Your last paragraph doesn't make much sense. What do you mean by "created as admin"? Created by admin?
In the Internet/Extranet workflow, the only difference between Private and Internal states is that "Members" can not view private content - but Editors can modify it and Contributors can view it.
Go to /portal_workflow/intranet_workflow/states/manage_main in your site to see the various Role-to-permission mappings