×

    Filters

    Didn't find what you were looking for?

    Extend your Search in Community

    Questions?

    We're always happy to help with questions you might have. Contact Us

Results

User Accounts Overview

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    System Manager / DevOps  |  Updated in v19.05 This feature was updated in v19.05.

A user account is part of the Journey Manager security management system, which allows for fine-grained control based on user's functions, roles and access permissions. Before users can log in to a form space, which requires authentication, they must have a valid user account. Manager allows an administrator to create a user and grants that user access to one or more form spaces. A user receives an email with login credentials, such as a username and password, so the user can access the form space's forms. Anonymous (unauthenticated) users can access forms if a form space is configured to allow anonymous access. An example of a form space that allows anonymous access is the Web Plug-in form space.

Note

Both the authenticated and anonymous (unauthenticated) users can access forms.

You can grant standard roles to users to control their access to and define capabilities at their form spaces. Each form space has a set of roles that can be granted to a user. You can create a new role as needed.

A typical form user must only be granted access to a form space where forms are hosted. This allows self-registered users immediate access to forms. However, most users must have an access to:

When working with user accounts, you should consider the environment that users are accessing, which can be production, development, or testing environment. Manager is designed to be customizable to accommodate enterprise’s security configurations and policies. The following users require access to a production environment:

  • Form users to access, complete and submit forms.
  • Operational staff to monitor and manage transactions and collaboration jobs.
  • Administrators to manage the environment and keep it secure.
  • System managers to view and analyze transaction reports.
  • Reviewer or manager to approve or reject customer form applications.

The following users require access to a development and test environments:

Users can only log into a form space if their user accounts are assigned to that form space. It is not possible to assign a form space to a user account when the form space is only accessed anonymously.

The following users should have access to form spaces:

  1. Form users to log into a form space.
  2. Form Builders to log into one or more form spaces:
  3. Administrators to log into Manager.
  4. Testers to log into various form spaces.
  5. Operators to log into Manager.
  6. Managers to log into one or more form spaces:
    • Journey Analytics
    • Business Reports
    • Salesforce
    • Workspaces

A standard user account contains the following information:

  • Credentials - username and password.
  • User type - a security managers used in your form space, which can be Local, LDAP or SSO.
  • User profiles - user contact details. A user can have more than one user profile containing different contact details.
  • Form spaces - assigned to the user to authorize access to specific form spaces.
  • Organizations - assigned to the user to authorize access to specific organizations. Applies to modules, but not relevant for form spaces.
  • Roles - grants individual roles which specify fine-grained permissions to access Journey platform and form spaces .
  • Groups - belongs to an individual group for authorizing access to restricted forms, receive alerts and notifications pertaining to a group.

Manager enforces some extra security rules to ensure that users cannot access restricted content, such as organizations, groups, users, forms, transactions and collaboration jobs.  |  v19.05 This feature was introduced in v19.05.

Next, learn how to view user accounts.