-
Type:
Suggestion
-
Resolution: Low Engagement
-
None
-
Component/s: Customer Organisation
-
None
-
0
Currently,
Users must be manually added or removed from an Organization in Jira Service Desk.
This is a separate action from creating a user, or adding a user to a group.
Today we use ldap groups to control access to Project access.
Example.
Groups = Project-1-Agents, Project-2-Agents, Project-1-PortalUsers
In Project Settings/Users & Roles:
For Project 1 we have Project-1-Agents in the Service Desk Team Role for Project 1, and Project-1-PortalUsers in the Service Desk Customer role
For Project 2 we have Project-2-Agents in the Service Desk Team role
Finally in Project Setting/Permissions we give the Service Desk Team role all the permission we want an Agent to have.
The net effect of the above approach is when we create and ID and put that ID in the appropriate groups they automatically get access to the JSD Projects they need. However, any Portal Users in Project-1-PortalUsers that need to be in an organization have be manually added to the organization.
The suggestion is to someone enable Organization membership to be tied a group.
If we had an Organizations in Project 1, called PortalUser-USA, PortalUser-Europe we'd like to be able to have a group named PortalUser-USA, PortalUser-Europe, and have the organization memmbership automatically match the group membership.
- mentioned in
-
Page Loading...