Jira client access how to#
Jira client access license#

They usually belong to internal teams in your organization and they occasionally assist agents with customer requests by making internal comments. CollaboratorsĬollaborators are licensed users in your Jira site whom agents in Jira Service Management work with.

Share requests with other customers (if allowed by customer permissions) To use a REST API, your application makes an HTTP request and parse the. Raise requests through the portal, email, or widget Jira REST APIs provide access to resources (that is, data entities) via URI paths. For example, employees who raise requests to an internal service desk will have access to the portal with no product access to the project are usually internal customers. CustomersĬustomers are unlicensed users who send requests to your service project through the portal, email, or widget.

Jira client access how to#

Learn how to add an agent to your service project. View, create and manage content in the knowledge base View, add, edit and delete customer-facing and internal comments on issues View the portal, queues, reports and SLA metrics within a service project Agents are added to the Service Desk Team role in your service project. Set up portals, request types, queues, reports and SLAsĪgents are licensed users who work on customer requests and add customers to the service project. Manage users and roles in service projects Project administrators for your service project can:Īccess all features in Jira Service Management Project administrators are licensed users who set up the service project and users. Unlicensed users can interact with your service project for free. Project permissions depend on the portal-only customer access settings, which means you can have different customer permissions for a service project depending.

Jira client access license#

Licensed users require a Jira Service Management license to interact with your service project. Jira Service Management has licensed and unlicensed users: Users in your service project are people who work on or send requests. And then assign the appropriate project roles ( Managing Users). This will allow you to assign Clients on a per Project basis, and therefore make sure that what Client A sees is not Client B's work.Jira Service Management has various user types and roles based on a combination of licensing, global permissions and project permissions.

Your final step is to add the users: Add users.All users inherit the JIRA users permission so you should remove any of the permissions that you do not want the clients to have (and ensure the developers/other roles have those permissions).The Permissions that you typically want to configure are: Browse Projects, Create Issues, Assign Issues, Assignable User, Close Issues, Add Comments, Edit Own Comments, Delete Own Comments, Create Attachments, Delete Own Attachments At this time you can also configure the permissions for other roles in the projects such as Developers. After the role is defined, you need to edit permissions to ensure the client users have appropriate permissions (click here for information on Managing Project Permissions).Name this role 'Clients' and give it a description 'A project role that represents clients in a project'. Create a new Project Role (for how to add a project role click here: Managing Project Roles).This has limitations - email notifications will not work and these users won't be able to see a project's status. If you do decide to setup the clients as seated users, then you will want to follow these steps to make sure that the client only has access to appropriate information: If you want to have clients be able to log into your system and see specific information, check statuses, etc., they will need to be a seated user (that is they count as one of your licensed users). You can set up JIRA to allow for anonymous users to create issues and even further allow this to happen via email without having the clients be seated users.