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; } } }

Restrict Access to commercialy sensitive pages in a project

oskfel_po

Hi,
Is there a way of restricting access to certain pages within a project, for example, to admistrators only?

For example - forms, goals or summary pages?

It seems incredible that the only level of granularity is to turn the feature on or off for everyone who has access to the project.
Am I missing something?

Thanks in advance,

Simon

Accepted answers

Tuncay Senturk _Snapbytes_

Hi @oskfel_po

Page level access restriction isn't a built-in feature for project-specific pages like forms, goals, or summary pages. Instead, the access is given at the project permission level.

You may want to check out ProForma Forms for Jira app.

All comments

Tuncay Senturk _Snapbytes_

Hi @oskfel_po

Page level access restriction isn't a built-in feature for project-specific pages like forms, goals, or summary pages. Instead, the access is given at the project permission level.

You may want to check out ProForma Forms for Jira app.

oskfel_po

Thanks for you fast reply @Tuncay Senturk _Snapbytes_

Im really surprised by that. Just by way of one example, we have Slack integration, and it would appear that anyone who has access to the project can add their channel - no admin access needed!

We have just started to use the releases feature and anyone with project access can create their own releases and add issues to any release! This could cause chaos if abused {shrugs}

May I kindly ask why you suggest Proforma Forms?

Tuncay Senturk _Snapbytes_

Hi @oskfel_po

You're absolutely right. Atlassian's focus is more on project- or issue-level permissions. Proforma allows you to define who (based on their roles, groups, or the issue type) can see or interact with specific forms. You can configure a form so that regular users might be able to see issues or forms but won’t be able to edit or submit them. I am not expert on Proforma but I know many companies started using it and relieved their painpoints.

oskfel_po

@Tuncay Senturk _Snapbytes_ - thanks again for your response.

We have managed the granularity for permissions on issue and field access using a combination of groups / roles together with behaviour and event listener scripts (ScriptRunner).

However, I'm not aware of how to apply these to urls (I assume its not possible) and that would thereby restrict certain users / roles accessing project features,

I appreciate your suggestion re: ProForma, but unless it could restrict features i.e. redirect a feature url, it won't move us forward in that direction.

I'm hoping sopmeone in the community has figured it out :-) and will post a solution {fingers crossed}

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud