With these settings in place, the project admin can restrict portal access to specific existing customers who are explicitly added to the service project: Select Don’t allow customers to create accounts. Under Jira Service Management, select Customer access. This would mean that only customers with an existing account or customers that your team adds will have access to your service project’s portal. Set up portal access for existing customers explicitly added to your service projectįirst, a site admin must make sure that customers can’t create their own accounts on your site. Under Service project access, choose Anyone allowed on the customer access settings. With these access settings in place, the project admin can restrict portal access to all existing customers or customers that your team adds to the service project: Select Don’t allow customers to create their own accounts. This would mean that only customers with an existing account or customers that your team adds will have access to your service project’s portal.įrom the top right of your screen, select Settings ( ) > Products. Set up portal access for customers with an account on your siteįirst, a site admin should make sure that customers can’t create their own accounts on your site. Under Service project access, choose Customers added to this service project only by agents and admins. To set up portal access for customers added to your service project:įrom your service project, go to Project settings > Customer permissions. You need to be a project admin to set up portal access. Set up portal access for customers added to your service project Restricted access to existing customers who are explicitly added to the service project Restricted access to customers who have an account on your site Restricted access to new customers who are explicitly added to the service project There are four main levels of access you can give your customers: Learn how to configure issue types for different projects.You can set permissions to define who can access and send requests to your service project through your portal. For example, if you have several different clients who send bug reports to your team, you will just need one bug report issue type that is present across all those request type groups. ![]() You can set up issue types to exist across multiple request type groups. Learn how to customize the fields of a request type. You can, then, query against this criteria for reporting purposes, SLAs, queue building, and more. You can add a field for the agent (or the customer) to fill in when raising a request that would associate the issue with a specific client. Adding an identifying criteria on the request ![]() You can name the request type group after the client to make it easy for them to navigate to the proper place and find the right request forms. There are a few different ways to use a single service project to serve multiple clients. Use a single service project to serve multiple clients Learn how to set up portal access.īrand your portal to suit your organization’s and client’s needs. This will make sure that those not on this customer list will not see this specific portal in the help center. Set up permissions to allow portal access to only customers who are added to the service project. Start by creating a service project for a specific client. Set up different service projects for each client Use a single service project and group request types based on clients Set up different service projects for each one of them, or If your organization is serving multiple clients, you can either: With a single license of Jira Service Management, you can create as many service projects and portals as you like.
0 Comments
Leave a Reply. |