Siebel Business Rules Administration Guide > Configuring the Business Rules Development Environment >

Managing Users and Groups in HaleyAuthority

By default, HaleyAuthority has three user groups - Administrator, Everyone, and Owners. You can control access by individual users in a group by assigning privileges and permissions to the group.

Each group has a set of privileges that define high level access control. By default, a member of any of these groups has all privileges. The privileges include:

• Take ownership
• Change privileges
• Generate logic
• Change default permissions
• Administer users and groups
• Rollback or commit
• Change workflow states
• Change custom fields

In addition, permissions can be assigned to each group to define access control at the object level. A permission restricts or allows each member of a group to perform certain actions on particular object types or on individual objects. For example, users in the Everyone group may be disallowed from deleting relations or disallowed to delete and individual relation.

For an object that is a child of another object, the permissions on the parent object are inherited by the child.

The following notable principles apply to users of a knowledge base:

• The network user (the Windows network login) who launches HaleyAuthority and defines the new knowledge base automatically becomes a member of the Administrators group in the new knowledge base.
• Any user (Windows network login) who opens the knowledge base automatically becomes a member of the Everyone group.
• Any user who runs the object importer and, as a result, a new HaleyAuthority entity, value, or relation is created, becomes the owner of the created objects. Privileges assigned to owners of objects are administered in the Owners group.
• By default, a member of any group can create new groups and can change the privileges of any group.

It is recommended that an appropriate administrator change the privileges of the groups to limit actions of individuals as your organization prefers. For example, it is not advisable for everyone to be able to redefine privileges for others, so you may want to change the default behavior by deleting the administer users and groups and change privileges privileges from the Everyone and Owners groups and leave those privileges to Administrators only.

CAUTION:  For restrictions on HaleyAuthority knowledge base modifications that are required for Oracle support, see This appendix provides technical support guidelines and troubleshooting information. The appendix contains the following topics:.

For detailed information on the following topics, and on other HaleyAuthority security topics, see HaleyAuthority Help.