![]() Instead of logging into an account, customer requests are tracked using an email address they provide. If you use a login free portal, customers can find the portal and it's help articles via search engines. Go to a project's customer permissions page and select the "Anyone on the web" option. Choose "Yes" for the questions, "Can customers create their own accounts?" and "Can customers access and send requests without logging in?" Then, a project administrator needs to allow anyone to send requests to the project. The setting is on the configuration page, in the products admin area in Cloud. First, a Jira application administrator needs to enable it. In Cloud, there are two steps to allow customers to create requests without an account. ![]() You can configure the customer portal to be login free. In JSM Cloud, customers can be anonymous, have accounts, or they can create requests without logging in. In JSM Server and Data Center, customers need an account to log in. So, any issues will show the word "anonymous" in the reporter field. In JIRA Software, anonymous users can view, browse, and create issues, but the users cannot be identified. All products support anonymous access, except the free versions in Cloud. Here are the user types in JIRA Software and Jira Service Management. Let's look at the user type differences across multiple Atlassian applications. Agents are licensed and customers are not. Jira service management has a different model, however. In most Atlassian applications, all named users need a license to use the product. ![]() As previously defined, Jira service management has different types of users, agents, and customers.
0 Comments
Leave a Reply. |