Project-based Authorization

Introduction

A project is a class that was assigned with project behavior. There are two types of projects in SmarTeam:

Regular projects will be used in cases where the project and its objects are not confidential.

An object can be related to a project in two ways :

This approach supports the concept that an object may be linked to a restricted project but in the same time not take its authorizations (for example, standard items should be accessible to everybody although they may be linked to secured projects too).

The Project Manager defines the users in the project and the roles they receive. When an object is attached to the project for the first time, it can be secured. Once it is secured, it can only be changed by the person who has "Share Secured By" authorization (as set in the User Maintenance option).

For details on the relationship between Users, Objects and Projects, see Associating Objects to a Project.

Note: The term "global security" refers nto all SmarTeam security that was implemented before project-based authorizations were added.

All permissions, roles and groups settings are taken from the SmarTeam - Editor settings. See SmarTeam - Editor Online Help for details.