nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Give customer access to the portal with Automation

Luka Popovic_iv0vcu

Hello everyone, is there a possibility to give customer access to a certain portal automatically, using automation rule?

Example would be - Customer creates an issue, if his email matches the conditions, he would be automatically added to the correct portal.

Accepted answers

Jack Brickey

Hi @Luka Popovic , so Automation occurs after an issue is created and unless you have your project configured as public access then the user creating the issue must already be a customer of the project. Now, if your project does happen to be public, there are possibilities do use automation to qualify the individual that created the issue. I wrote an article in the community about a year ago on this. I will see if I can find it if that is of interest to you. Please let me know.

All comments

Jack Brickey

Luka Popovic_iv0vcu

Yeah this was my concern, because I created two projects, one that only serves for customers to request access and the other one would be locked, if access is gained they would be added there, the scope of the rule is set to these two projects but when testing it didn't work out how I thought it would.

It seems that I will have to find another way to do this because everything is currently done manually, if you have any suggestions or ideas on how to add users trough automation to two or one project that is not public it would be great help.

Thank you for your response!

Jack Brickey

Hi @Luka Popovic ,

so you have a open project where users can request access is that correct? Furthermore, based on the users email address, you would add them as a customer to another project is this correct? Assuming so I'm wondering if there may be a way to do that. Would you mind sharing the rule that you were trying to get to work? There is an action to add a customer to a project as shown below. I think the key here is that you need to create an organization for your project, and you would add the customer to that organization, allowing them to have access. I would be interested to know where your automation was falling short. I could try to set up a test automation rule for this, but would like to ensure I'm on the right path before I do.

Luka Popovic_iv0vcu

This "Add new customer" rule seems like it escaped me somehow, weird. I will check, meanwhile this is the rule currently:

(Could you please guide me in order to set it up, the idea was to add a new customer which will be automatically put into the organization that has the same name as the email domain name of the customer, or the organization will be created if it already doesn't exist with their domain name?)

Screenshot 2023-07-10 155044.png

Thank you again for the detailed information!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management