Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home Paris Now Platform Capabilities Now Platform capabilities Flow Designer Content filtering for Flow Designer

    Content filtering for Flow Designer

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Content filtering for Flow Designer

    Specify what content a user can access based on the user's role.

    Display only content that is relevant for a particular user, hiding content that is unnecessary or sensitive. For example, if an hr_manager in human resources is creating a flow, show only the set of actions and subflows that are relevant to HR cases.

    Content filtering uses:
    • Content definitions to specify types of content.
    • Content filtering rules to determine who can access the content.
    Flow Designer includes several default definitions and filtering rules. Set up content filtering by modifying pre-existing rules or creating your own.

    Content definitions

    Content definitions specify a type of Flow Designer resource. Resources are the key components of Flow Designer, such as triggers, actions, and subflows. Create definitions to include an entire resource, or refine your definitions through conditions. For example, you can create a definition that includes all flow triggers, or you can use conditions to include only triggers with a category of date.

    You can further refine content definitions through tagging. Add tags to items in a resource list, then design your content definition to only include resources with that tag.

    Content filtering rules

    Content filtering rules specify the role a user must have to access the content in a particular definition. Each rule associates a single user role with a single content definition. When a user accesses Flow Designer, filtering rules determine what content the user may access based on the user's role.

    Read-only flows

    Users may be able to view a flow, subflow, or action containing components that they can't normally access. For example, a flow that's visible to a user might include an action the user wouldn't usually be able to view. When a flow contains a restricted component, the entire flow becomes read-only. Users can run the flow but can't modify or copy it.

    Table 1. Access summary
    Resource filtered User has role User does not have role
    Flow
    • The flow is visible to select during design.
    • The flow can be copied.
    • The flow can be modified.
    • The flow is hidden and cannot be selected during design. For example, the flow is hidden when creating a Process Automation Designer activity definition.
    • The flow cannot be copied.
    • The flow is read-only.
    Trigger
    • The trigger is visible to select during design.
    • Any flow that includes the trigger can be copied.
    • Any flow that includes the trigger can be modified.
    • The trigger is hidden and cannot be selected during design.
    • Any flow that includes the trigger cannot be copied.
    • Any flow that includes the trigger is read-only.
    Subflow
    • The subflow is visible to select during design.
    • Any flow that calls the subflow can be copied.
    • Any flow that calls the subflow can be modified.
    • The subflow is hidden and cannot be selected during design.
    • Any flow that calls the subflow cannot be copied.
    • Any flow that calls the subflow is read-only.
    Flow logic
    • The flow logic is visible to select during design.
    • Any flow that includes the flow logic can be copied.
    • Any flow that includes the flow logic can be modified.
    • The flow logic is hidden and cannot be selected during design.
    • Any flow that includes the flow logic cannot be copied.
    • Any flow that includes the flow logic is read-only.
    Action
    • The action is visible to select during design.
    • Any flow that includes the action can be copied.
    • Any flow that includes the action can be modified.
    • The action is hidden and cannot be selected during design.
    • Any flow that includes the action cannot be copied.
    • Any flow that includes the action is read-only.
    Step
    • The step is visible to select during design.
    • Any action that includes the action can be copied.
    • Any action that includes the step can be modified.
    • The step is hidden and cannot be selected during design.
    • Any action that includes the step cannot be copied.
    • Any action that includes the step is read-only.
    • Configure content filtering definitions

      Specify which content a user can access by creating content definitions.

    • Configure content filtering rules

      Use content filtering rules to specify the role a user must have to access content.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Content filtering for Flow Designer

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Content filtering for Flow Designer

      Specify what content a user can access based on the user's role.

      Display only content that is relevant for a particular user, hiding content that is unnecessary or sensitive. For example, if an hr_manager in human resources is creating a flow, show only the set of actions and subflows that are relevant to HR cases.

      Content filtering uses:
      • Content definitions to specify types of content.
      • Content filtering rules to determine who can access the content.
      Flow Designer includes several default definitions and filtering rules. Set up content filtering by modifying pre-existing rules or creating your own.

      Content definitions

      Content definitions specify a type of Flow Designer resource. Resources are the key components of Flow Designer, such as triggers, actions, and subflows. Create definitions to include an entire resource, or refine your definitions through conditions. For example, you can create a definition that includes all flow triggers, or you can use conditions to include only triggers with a category of date.

      You can further refine content definitions through tagging. Add tags to items in a resource list, then design your content definition to only include resources with that tag.

      Content filtering rules

      Content filtering rules specify the role a user must have to access the content in a particular definition. Each rule associates a single user role with a single content definition. When a user accesses Flow Designer, filtering rules determine what content the user may access based on the user's role.

      Read-only flows

      Users may be able to view a flow, subflow, or action containing components that they can't normally access. For example, a flow that's visible to a user might include an action the user wouldn't usually be able to view. When a flow contains a restricted component, the entire flow becomes read-only. Users can run the flow but can't modify or copy it.

      Table 1. Access summary
      Resource filtered User has role User does not have role
      Flow
      • The flow is visible to select during design.
      • The flow can be copied.
      • The flow can be modified.
      • The flow is hidden and cannot be selected during design. For example, the flow is hidden when creating a Process Automation Designer activity definition.
      • The flow cannot be copied.
      • The flow is read-only.
      Trigger
      • The trigger is visible to select during design.
      • Any flow that includes the trigger can be copied.
      • Any flow that includes the trigger can be modified.
      • The trigger is hidden and cannot be selected during design.
      • Any flow that includes the trigger cannot be copied.
      • Any flow that includes the trigger is read-only.
      Subflow
      • The subflow is visible to select during design.
      • Any flow that calls the subflow can be copied.
      • Any flow that calls the subflow can be modified.
      • The subflow is hidden and cannot be selected during design.
      • Any flow that calls the subflow cannot be copied.
      • Any flow that calls the subflow is read-only.
      Flow logic
      • The flow logic is visible to select during design.
      • Any flow that includes the flow logic can be copied.
      • Any flow that includes the flow logic can be modified.
      • The flow logic is hidden and cannot be selected during design.
      • Any flow that includes the flow logic cannot be copied.
      • Any flow that includes the flow logic is read-only.
      Action
      • The action is visible to select during design.
      • Any flow that includes the action can be copied.
      • Any flow that includes the action can be modified.
      • The action is hidden and cannot be selected during design.
      • Any flow that includes the action cannot be copied.
      • Any flow that includes the action is read-only.
      Step
      • The step is visible to select during design.
      • Any action that includes the action can be copied.
      • Any action that includes the step can be modified.
      • The step is hidden and cannot be selected during design.
      • Any action that includes the step cannot be copied.
      • Any action that includes the step is read-only.
      • Configure content filtering definitions

        Specify which content a user can access by creating content definitions.

      • Configure content filtering rules

        Use content filtering rules to specify the role a user must have to access content.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login