Skip to main content
Insert Banner Message here.

Community

Search

Welcome to Community

Ability to restrict access to Web Action

Answered

Comments

6 comments

  • Radoslaw Nocon

    This is a very good suggestion, This would help us too!

    0
  • Adam McMillan

    In 20R2 (July 31, 2020) we aim to release a feature that will allow you to control which roles have access to specific user actions defined in your document lifecycle state.

    I do not think, however, there are any plans to introduce a "condition" that checks for the existence of a specific document relationship. That's the first time I've heard of that kind of a requirement. Would you be able to describe the use case a bit more there?

    0
  • Borovsky, Jindrich

    Hi Adam, thanks for the response. Regarding the second use case - we have a content authoring application that opens up from PromoMats via the web action. That application only works for content in a specific format (modular content). So we have a placeholder with modular content (including some technical assets - project file, templates etc.) associated in Components section (on the material). At the same time we have materials created the old way - i.e. just the pdf for med-legal review and few assets that are not modular though. So we have a mix of resources/materials in our Vault - modular and non-modular. Obviously we want that web action (for our content creation tool) to show in the actions menu only when there is modular content associated in Components section on the Material... It should not be showing for Materials that cannot be opened/edited in that tool. Hope this makes sense...

    thanks,

    Jindrich

    0
  • Adam McMillan

    And that's controlled by Country?

    I think if you have your configuration as:

    • User action defined on the lifecycle state, but as a conditional user action, based on Country
    • and
    • also control that action in the (upcoming) atomic security tab on the doc lifecycle, where you can say which role can execute the action

    so the Country condition is configured on the action itself, and the availability of the action for specific roles is configured in the new Atomic Security tab. In that case you'd probably get what you need? Might be worth us touching base again after you've got your hands on a limited release vault, or after the 20R2 general release.

    0
  • Borovsky, Jindrich

    Hi Adam,

    apologies if I was not clear. It is not controlled by a Country. In our Vault we have a mix of materials that are Modular and Non-Modular, regardless the Country. However the web action for content authoring tool should be available (in actions menu) only for Materials that are Modular (now it shows up for Non-Modular resources too) - that is not defined by a metadata field but rather by specific content (project files, image components etc.) associated in Components section. Hope this clarifies...

    Anyway restricting it down to specific users will help tremendously as well... looking forward to that...

    thanks,

    Jindrich

    0
  • Adam McMillan

    Understood, thank you for the clarification.

    0

Please sign in to leave a comment.

Powered by Zendesk