{"id":2931,"date":"2026-09-04T10:12:46","date_gmt":"2026-09-04T10:12:46","guid":{"rendered":"https:\/\/viaspaces.com\/Documentation\/working_in_teams_gutenberg\/"},"modified":"2026-09-04T10:13:43","modified_gmt":"2026-09-04T10:13:43","password":"","slug":"working_in_teams","status":"publish","type":"docs","link":"https:\/\/viaspaces.com\/sk\/Documentation\/working_in_teams\/","title":{"rendered":"Working in Teams"},"content":{"rendered":"\n

Nest groups, scope access with filters, and combine every access layer at once.<\/em><\/p>\n\n\n\n

This builds on Users and Access Rights, which covers Users, User Groups, and Roles. Here we cover the advanced options: nesting groups, filtering access down to individual records, and how everything combines.<\/p>\n\n\n\n

Nested Subgroups<\/h2>\n\n\n\n

A User Group’s Subgroups<\/strong> field lets you nest other existing groups inside it, so you can build access in layers instead of one flat list.<\/p>\n\n\n\n

    \n
  1. Open Settings, User Management, Groups<\/strong>.<\/li>\n\n\n\n
  2. Click Add New Group<\/strong>, or open an existing one to edit it.<\/li>\n\n\n\n
  3. In Subgroups<\/strong>, select one or more groups to nest inside this one.<\/li>\n\n\n\n
  4. Click Save<\/strong>.<\/li>\n<\/ol>\n\n\n\n
    \n

    \u26a0\ufe0f Needs verification<\/strong><\/p><\/p>\n\n\n\n

    Whether nesting a group extends the parent’s roles and workspaces down to the subgroup’s members, or works the other way around, isn’t confirmed yet.<\/p>\n<\/div>\n\n\n\n

    Field-Level Access Filters (Optional Settings)<\/h2>\n\n\n\n

    Optional Settings narrows what a user or group can see within an object type, using a predicate \u2014 an expression that’s true or false for each record. Only records where it’s true stay visible. It’s available on both the Edit User panel and the Add\/Edit Group panel.<\/p>\n\n\n\n

    Use a filter to go further than a role and workspace alone allow \u2014 for example, limiting a Reader role to business partners in one region only.<\/p>\n\n\n\n

      \n
    1. Open Optional Settings<\/strong> on the Edit User or Add\/Edit Group panel and click Add Filter<\/strong>.<\/li>\n\n\n\n
    2. Name the filter and choose a Permission Object: Business Partners, Projects, Items, or Workspaces.<\/li>\n\n\n\n
    3. Write the Predicate and click Validate<\/strong>.<\/li>\n\n\n\n
    4. Click Add<\/strong>, then Save<\/strong>.<\/li>\n<\/ol>\n\n\n\n
      \n

      \u2139\ufe0f Good to know<\/strong><\/p><\/p>\n\n\n\n

      For Workspaces, you can target a specific workspace or use the special value general<\/strong> to cover anything not otherwise targeted. Exact matches are checked before general ones.<\/p>\n<\/div>\n\n\n\n

      Predicate Syntax<\/h3>\n\n\n\n

      Predicates reach into an object’s fields with dot notation, like document.header.documentTypeId<\/code>, and index arrays with brackets, like document.auditLog[0].time<\/code>. A caret counts from the end \u2014 [^1]<\/code> is the last item \u2014 and a range like [2..]<\/code> or [..^2]<\/code> selects a slice.<\/p>\n\n\n\n

      Operator<\/th>Meaning<\/th><\/tr><\/thead>
      .<\/code><\/td>Path delimiter, or a decimal point<\/td><\/tr>
      ()<\/code><\/td>Groups an expression, or holds function arguments<\/td><\/tr>
      []<\/code><\/td>Accesses an array item<\/td><\/tr>
      {}<\/code><\/td>Defines an array<\/td><\/tr>
      ++<\/code>, --<\/code><\/td>Increment or decrement<\/td><\/tr>
      !<\/code><\/td>Logical negation<\/td><\/tr>
      +<\/code><\/td>Addition or string concatenation<\/td><\/tr>
      -<\/code><\/td>Subtraction, or a negative value<\/td><\/tr>
      ?:<\/code><\/td>Ternary if-then-else<\/td><\/tr>
      ,<\/code><\/td>Argument separator<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n

      \u26a0\ufe0f Needs verification<\/strong><\/p><\/p>\n\n\n\n

      The in-app Help lists this reference as incomplete \u2014 a dictionary-style key lookup, a null-safe traversal operator, and a way to hide a filter from the document’s other side are all listed as not yet available.<\/p>\n<\/div>\n\n\n\n

      Combining Workspaces, Groups & Roles<\/h2>\n\n\n\n

      A role sets what a user can do, a workspace sets which documents they see, and a User Group bundles both across many users at once. A predicate filter adds a fourth layer on top, narrowing things down to specific records.<\/p>\n\n\n\n

      Put them together for scenarios none of them can express alone \u2014 for example, a subgroup with a Reader role, scoped to one workspace, further limited by a predicate to business partners in one region.<\/p>\n\n\n\n

      \n

      \u26a0\ufe0f Needs verification<\/strong><\/p><\/p>\n\n\n\n

      The Partners<\/strong> field on the Add\/Edit Group panel appears disabled by default, and what enables it isn’t confirmed yet.<\/p>\n<\/div>\n\n\n\n

      Default Groups on a New Account<\/h2>\n\n\n\n

      Every new account starts with a set of default User Groups already in place, which an administrator can edit or delete.<\/p>\n\n\n\n

      \n

      \u26a0\ufe0f Needs verification<\/strong><\/p><\/p>\n\n\n\n

      Which groups and roles ship as the platform default isn’t confirmed yet \u2014 what you see in Settings, User Management, Groups may just reflect this account’s own setup.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

      Nest groups, scope access with filters, and combine every access layer at once. This builds on Users and Access Rights, which covers Users, User Groups, and Roles. Here we cover the advanced options: nesting groups, filtering access down to individual records, and how everything combines. Nested Subgroups A User Group’s Subgroups field lets you nest […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"iawp_total_views":0,"footnotes":""},"doc_category":[59],"glossaries":[],"doc_tag":[],"class_list":["post-2931","docs","type-docs","status-publish","hentry","doc_category-documentation"],"year_month":"2026-09","word_count":552,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"Veronika Nedecka","author_nicename":"veronika-nedecka","author_url":"https:\/\/viaspaces.com\/sk\/author\/veronika-nedecka\/"},"doc_category_info":[{"term_name":"Documentation","term_url":"https:\/\/viaspaces.com\/sk\/docs-category\/documentation\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/docs\/2931","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/comments?post=2931"}],"version-history":[{"count":1,"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/docs\/2931\/revisions"}],"predecessor-version":[{"id":2932,"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/docs\/2931\/revisions\/2932"}],"wp:attachment":[{"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/media?parent=2931"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/doc_category?post=2931"},{"taxonomy":"glossaries","embeddable":true,"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/glossaries?post=2931"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/viaspaces.com\/sk\/wp-json\/wp\/v2\/doc_tag?post=2931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}