User permissions for drafts
Users need special permissions to create drafts and to access the draft state flow. You set up permissions through the User group policies. State flows dictate how drafts are merged into originals. They are enabled for any definition that uses the drafting functionality. The standard draft state flow only allows M.Builtin.Approvers or superusers to approve a draft entity.
To configure the Drafts feature, you must either be a superuser or have the necessary permissions granted to you through user group policies.
Add users to the M.Builtin.SM.Everyone user group
To add users to the user group for drafts, you must add them to the M.Builtin.SM.Everyone user group. This can be done in one of the following ways:
-
Adding a user to a group from the User groups tab. In this example, you select the M.Builtin.SM.Everyone user group to add users to.
-
Adding a user to a group from the Users tab. In this example, you select the M.Builtin.SM.Everyone user group in the Users tab.
Grant user permissions for drafts and draft state flows
To grant user permissions for drafts and draft state flows:
-
Assign the CreateDraft permission for the required entity definitions to the M.Builtin.SM.Everyone user group.
-
Assign M.Builtin.SM.Everyone access to the required portal pages.
-
Update the policy combination of the M.Builtin.SM.Everyone user group to include the correct policy combination.
The merge logic is used when a DraftLifeCycleToDefinition relation is set to the Done state after being approved by an M.Builtin.Approver or a superuser. This relation is defined as allow_update=false, which means you can only update it through the draft state flow.