Add yourself as a person (Business Administrator), then add a person defined as a System Administrator. The Business and System Administrators might or might not be the same person. Two persons are defined when you install the software:
These persons are not real users: they do not login to use the
apps.
Do not delete the
A person's access is determined by the licenses assigned to them and their security contexts. Users can also be added to groups, access roles, and associations that determine access. For more information, see User Categories and Hierarchies. Note:
A group is a set of people who are members of the same organization
and share information. They can share access to business objects for a common
reason, such as a particular project or functional skills. Within a group,
people of different talents and abilities act in different roles. Groups are
not supported by the baseline behavior.
Your access role is usually your job function. You might be a Manager, Purchasing Agent, Forms Adjuster, Writer, Editor, System Administrator, and so forth. A person can have more than one role within the 3DEXPERIENCE platform. For example, you might be both a Manager and an Editor. For baseline behavior, access roles are defined by level of access and not specific job functions. Access roles give you defined accesses to specific types of business objects. Your role can also restrict you from accessing business objects that you do not need. In addition, policies and rules restrict access to specific business objects and for specific attributes, programs, relationships, and forms. For more information, see People & Organizations and Content Configuration Guide: User Working Environment: Security Contexts. Another element of a person definition that can effect user access is the user type. For more information, see Type Clause for the Add Person Command. If a user’s type is System Administrator, the software performs no access checking. The system allows such a user to perform any task on any object, even if a policy or rule limits the user’s access. Assign the System Administrator user type only to people who need full access to all objects, such as a person who will import and export data or maintain vaults and stores. For such a user, you should also create a second person definition that is not assigned the System Administrator for their normal use. When performing routine work with business objects, the user should set the session context using this second person definition. If the user’s type is Trusted, the system allows the user to perform any task that requires read access only (viewing basics, attributes, states, or history for the object). You can define a person that does not represent a real person. For example, you could define a person to represent the company. When objects reach the end of their lifecycle and are no longer actively worked on, the system can reassign the objects to this person. Having the company person own inactive objects allows standard users to perform owner-based queries that return only objects that currently require the users’ attention. The Corporate person in 3DEXPERIENCE Platform software serves this purpose. You can also define persons who are not users of the system. These persons are useful for sending notifications to people outside the system or for maintaining history records associated with people who no longer work in the organization. | ||||||||