• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      The way Automation determines what Organization to map a user to (base on email) is brittle. It relies on assuming that the "first" email domain of the "first" user in the Organization is the domain to use for mapping Users to Organizations.

      This can fail when, for example, multiple email domains need to be shared by a single Organization.

      It would be better if there was a way to manually specify mappings (or rules as to how to perform the mappings) so that users would have more confidence as to how mappings will be performed.

            [JSDCLOUD-15409] Organization auto-mapping is brittle and prone to error

            There are no comments yet on this issue.

              Unassigned Unassigned
              jnavin James Navin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: