The associate database table represents employees, resources, and other users - except for external persons.
Yet, this table is important for understanding and navigating the relationship between a person and their user account as well as the relationship between employees at the organization running the CRM system and the external parties they interact with.
You may think of associates as the missing link that connects people.
|1||Resource||Not a person
|2||Anonymous||Not authenticated for SuperOffice|
(no person (1) + not authenticated (2) + no calendar (4)
|8||NoSentry||Has full access rights
The Sentry mechanism is bypassed
(no person (1) + no calendar (4) + full access/bypass sentry (8)
Frequently used values
|associate_id||ID (primary key)|
|name||Initials, sign-in name, database user name|
|group_idx||Primary group membership|
|ejuserId||ID of the user account
0 if not connected to an account
|lastlogin||The last time the associate signed in|
|lastlogout||The last time the associate signed out|
|registered||When the associate was registered|
|updated||The last time the associate was updated|
Resources are typically meeting rooms or equipment such as projectors.
|isLocation||True if it represents a location|
|locationAddress||The address, if it's a location|
Associate list and cache
In NetServer when you have a session, the session cache will contain a special cache entry named the associate cache. There all the associates listed in the SuperOffice database can be accessed through the cache, which is much faster than retrieving the associates from the database.
The associate list is an MDO list type that you can retrieve from the database. It holds all the associates from the SuperOffice database.