Creating the Permissions Structure

When setting up a permissions structure for KnowledgeTree in your organization, consider the following:

Note: In this case, metadata can be added to the fieldsets, instead of displaying client

information. Alternatively, configure options such as 'email separation by group'.

Note: Government agencies are typically expected to be highly secure, and most

organizations own confidential documentation that needs to securely stored and

accessed in the document management system. In both cases, external users should

be identified and prevented from accessing restricted areas of the repository.

Note: Permissions may be less important where the system is only used by internal users,

or where everyone requires access to all or most of the content in the repository.

Note: Units are useful where the organization prefers to split the administrative role

(e.g. by department, or by geographical regions). Units are manually created within

KnowledgeTree. They're not supported in Active Directory or LDAP, so they cannot be

imported into KnowledgeTree.

Note: Roles are a KnowledgeTree concept that are used to allocate permissions

on a document or folder to an individual user. Typically, permissions are granted

to the group, and thus to all users in the group.

Note: Dynamic permissions change, based on metadata.