Skip to main content

Namespaces

Namespaces allows for the grouping of custom objects in Avantra, and to grant permissions on objects assigned to Namespaces. Namespaces are what workflows and steps are assigned, meaning that different customers with the same requirements can be assigned to the same workflow or step, reducing the requirement to have duplicate workflows or steps.

Creating / updating a namespace​

Namespaces are created in the Configuration > Integrations menu under the tab Namespaces. You must be an administrator to create a namespace.

note

Once you create a Namespace you must assign it to any non-administrator users that intend to use it. Otherwise they cannot see the Namespace or interact with it.

Assigning an object to a namespace​

To add a Namespace to a workflow or step object, open the workflow or step and assign the Namespace in the corresponding field.

Permissions​

User permissions can now be granted on Namespaces as well.

Open Avantra user management and select the role you wish to assign permissions to. There you can see the assigned customers and the assigned Namespaces. ClickAssign Namespaces and set the available Namespaces. Users needing access to a workflow (or step) need permission on that Namespace through a role.

Workflow permissions:

  • A workflow has no customer, only a namespace.
  • User must have a correspondent view/edit/start permission on the namespace to view/edit/start the workflow.
  • User needs a start permission on the namespace AND customer to start a workflow.
  • Admin (root) has root permissions for all customers and namespaces by default

Namespace hierarchy​

Namespaces can be organized in a hierarchy. The hierarchy is based on a dot '.' notation.

For example, if we have the following namespaces:

  • avantra
  • avantra.systemcopy

Then avantra.systemcopy is a sub-namespace of avantra because the name starts with "avantra".

The consequence is that permissions granted on a higher level namespace, "avantra" in the above example, automatically get the same permissions on all defined sub-namespaces, "avantra.systemcopy" in the above example.