Daylite 3 introduces the new concept of teams to replace the 1.x permission system.

Teams are used to group users in order to specify who can see/change content in the database.

The important thing to know about teams is how the previous permission system in Daylite 1.x was migrated over to Daylite 3.

In Daylite 1.x, the concept of Peers, Directs, Assistant, etc. existed. In Daylite 3 there is an individual team which is associated with each of these permissions.

The way the migration works is that,

If Bob had a Contact whose permission was Peers, then a Bob-Peers team was created and each Contact which had this permission gives the new Bob-Peers team the appropriate read/write access (as specified in v1.x).

The same happens for Bob if he had an assistant. If a Contact had permissions given to Bob and his secretary in 1.x, then in v3, that Contact would give visibility to the Bob-Assitant team.

Teams can be managed in the Preferences, in the Users and Teams preference pane. Users can be added and removed to the Teams. A Super and Admin team exist. The difference between the Super and Admin teams is that the Super team can see everything in the database no matter what. The Admin team can see everything in the database except for "Private" content. If a Contact is private, that means that only the user who is the owner of the Contact can see it.

A public team exists which includes all users in the database. If you give a Contact the visibility of Public then all users can see this Contact (and edit it).

Read and Write access can be specified on a per Contact, Org, etc. basis by selecting Custom from the Visibility pop-up in the edit card for the Contact.

Also, an important thing to note, is that delete access can be restricted by unchecking the "Delete Objects" checkbox in the Permissions tab for a particular user. This can be specified on a per user basis.