Editing Persons and Users

Content Store person and user objects appear in CUE as special content items called Person content items. Person content items differ from other content items in the following ways:

  • They are predefined by the system, not user-defined as are all other types of content item.

  • They have a fixed structure, with a fixed set of fields that cannot be modified.

  • They are identified internally by the special name com.escenic.person, and this is the content type name you have to use in CUE's Document types search filter.

  • They are subject to a different workflow and cannot be published.

The difference between a person and a user is that a user has a Content Store login. When you open a Person content item you can see whether it represents a person or user by checking the User name field under General Info in the metadata panel.

Person content items cannot themselves be published, as they are considered to contain private information such as addresses and telephone numbers. Person content items do, however, have a Profiles relation, which you can used to associate ordinary, publishable content items with Persons. Profile content items can be used to hold images, biographical details and so on for use in bylines.

The recommended approach is to define a special "Profile" content type that contains fields/relations for all the information you want to be able to publish about authors: biography, email address, Twitter handle, headshot and so on. A Profile content item is then created for each Person object and dropped in its Profiles relation.

Assuming you have administrator access rights then you can use CUE to edit Person content items (for both persons and users). You cannot, however, create or delete them. To do these things you need to use Web Studio (see User Administration).

If you do not have administrator access rights then you can only edit your own user's Person content item or persons (not users) that you have created yourself.