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

Confiform Field Definition Options - restricting view and edit on the field itself doesn't get saved

Andre T.

I am trying to restrict view/access to a field I am creating. Every time I update and save the field options with certain users, my entry disappears when I re-open the field options a second time. Any idea why that is? Is this a bug with version of Confluence we are using?

I am using the Cloud version of Confluence.

Accepted answers

Himanshu Tiwary_go407r

Hi @Andre T_ ,

This sounds more like a limitation in Confluence Cloud than a bug. In Cloud, access is usually controlled at the space, page, or database level, not at the individual field level, so if you are trying to restrict one field to only certain users, Confluence may simply not support that setup. That would explain why the users disappear when you reopen the field settings, because the change is not being retained. So my guess is that this is expected behavior rather than a version issue.

If this helped, I’d really appreciate a Recognition.

All comments

Himanshu Tiwary_go407r

Hi @Andre T_ ,

If this helped, I’d really appreciate a Recognition.

Andre T.

We had Confluence Cloud previously as well and it was working fine. Did something change in recent releases of Confluence Cloud to break this existing feature?

By the way this is a feature of Confiform plugin so it would be great if we can get someone from the Confiform team to answer the ticket. Thanks!

Himanshu Tiwary_go407r

Hi @Andre T_ ,

Thanks, that changes the picture a lot. If this is a ConfiForms feature, then I would not treat it as a standard Confluence Cloud limitation anymore. In that case, if it worked before in Cloud and now the values disappear after saving, it is much more likely to be either a ConfiForms-side issue, a recent app change, or a compatibility change rather than native Confluence behavior.

So yes, something may have changed, but I would look first at the ConfiForms app version/configuration rather than Confluence itself. Since the field options are not being retained, it does sound like something is either no longer supported the same way or is not saving correctly anymore.

I agree with you that this is the kind of question the ConfiForms team should really answer, because they would be able to confirm whether this is expected, a regression, or a bug in the app.

Andre T.

Do I need to open a different ticket for confiform or will someone from that team be able to pick up and look into this ticket?

Himanshu Tiwary_go407r

H @Andre T_ i,

For something specific to ConfiForms, it is usually better to open a separate ticket directly with the ConfiForms team rather than wait here. Community posts can sometimes be seen by vendors or other users, but there is no guarantee that someone from the app team will pick it up quickly.

So if you want a proper investigation, I’d suggest raising it with ConfiForms support directly and sharing the same details there.

If this helped, please give it an upvote.

Welcome!

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

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

confiform