By default, the Developer comes with one empty master role list for each language installed. Each master role list can be used to assign roles to all documents of the same language. Therefore, you need to create a new role list only if your content includes a language for which no role list currently exists.
Note: Only one role list can be used to assign roles to documents of a given language. If multiple role lists exist for the same language, only the oldest (the first one created) is used to populate the role assignment selection list. For example, if you make a copy of the Roles.en document and add roles to it, those new roles do not appear as assignment choices for any English documents. Therefore, you should not create more than one role list for any language.
Warning! Do not delete the role list for any language. Doing so will disable role assignment for that language.
To create a new role list, you must start with an existing role list. For example, you can set up all necessary roles in an existing role list and then create new role lists for other languages using this initial list as a model.
Tip: You can change the language of a role list from the Properties toolpane.
You can create a new role list from the Library or the Role Editor. From the Library, you simply copy and paste the entire role list document. From the Role Editor, you save the original role list as a new document.
The original master role lists in the Library are named according to language. For example, the Roles.en document is the master role list for the English language. Although you do not have to follow this convention in naming new role lists, it is recommended that you provide a meaningful name so you can easily find the new role list later.
All role list documents must be saved in the System/Roles folder to be used for role assignment.
Multi-user Considerations
Any new document that you create or link is automatically checked out to you. If you want to make a new document available to multiple authors and place the document under the Developer's version control system, you must check it in.
See Check In and Check Out Documents in Use the Developer in a Multi-user Environment for more information.
To create a new role list from the Role Editor:
Although there are no restrictions on the name of a role list, it is recommended that you provide a meaningful name so you can easily find the new role list later.
Both the Type field and the Save in field should read "Roles".
To create a new role list from the Library:
You can also right-click your selection and choose Copy.
For steps 4 and 5, you can also right-click in a blank area in the Contents pane or right-click a folder in the Folders pane and choose Paste from the context menu. You can paste the new role list document in any Library folder, but it cannot be used for role assignment unless it is saved in the System/Roles folder.
Although this step is optional, it is highly recommended. There are no restrictions on the name of a role list, but it is recommended that you provide a meaningful name so you can easily find the new role list later.