Skip to main content

Select Secure Zones with permissions to access front end edit forms for modules and webapps.

Feature

We currently have "anyone can edit" or owner/creator can edit as options.

More commonly, a requirement would be that only members of a trusted Secure Zone would be allowed to edit front end.

Could we add a third option to modules/ webapps in Siteglide Admin, allowing us to officially set an array of secure zone ids which can access each webapp/module edit forms when logged in?

While this is possible already with custom code, adding built in support will be convenient and allow SiteBuilder support.

Posted by Matt Jones ·
3 comments

Log in to comment and vote

Comments3

  • Matt Jones

    •

    Aug 21

    •

    Merged request

    •

    3 votes

    Forms - Control which Secure Zone can submit

    Currently WebApp front end edit forms can either be submitted front-end by the item creator or anyone.

    It would be useful to restrict a form to only be able to be edited front end by certain Secure Zones.

    Would also be useful if this could overlap with item creator, where the creator or someone in an authorized secure zone can edit.

    It might be useful to allow a custom authorization policy for form endpoints too, making custom code with forms easier.

  • Matt Walter

    Team•

    Oct 24, 2024

    You can already put items in Secure Zones. Is that not enough, as the item (and thus the form) would only show if the user is logged in to that SZ?

    • Matt Jones

      •

      Nov 1, 2024

      I don't think so, as read and write permissions would normally be different.

      E.g. most of the reason for wanting to control edit access would be to make sure the quality of public-facing content was good, so in that case you'd want to have items displaying front end to a wider audience than you would want to give permission to edit. With your solution, if you added an item to a secure zone to restrict editing, it would disappear from public view.

      You could add another secure zone field per item for edit access instead of globally for the webapp/ module. That's a possible choice.