Location type rules and behaviour
For every parent Location type in the left column, you can see its possible member Location types under Members.
| Parent | Members | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Unknown | Organisation | Group | Position | Person | Project Team | Committee | Venue | Workgroup | Storage Provider | |
| Unknown | - | - | - | - | - | - | - | - | - | - |
| Organisation | - | Yes | - | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Group | - | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | - |
| Position | - | - | - | - | Yes | - | - | - | - | - |
| Person | - | - | - | - | - | - | - | - | - | - |
| Project Team | - | - | - | Yes | Yes | Yes | - | Yes | - | - |
| Committee | - | - | - | Yes | Yes | - | Yes | Yes | - | - |
| Venue | - | - | - | - | - | - | - | - | - | - |
| Workgroup | - | - | - | Yes | Yes | Yes | Yes | Yes | - | - |
| Storage Provider | - | - | - | - | - | - | - | - | - | - |
- All Location types except Unknown, Workgroups can be external or internal
- Workgroups can only be internal
- Unknown Location types can only be external
For every supervisor Location type in the left column, you can see the possible Location types they can be supervisors of under Supervised.
| Supervisor | Supervised | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Unknown | Organisation | Group | Position | Person | Project Team | Committee | Venue | Workgroup | Storage Provider | |
| Unknown | - | - | - | - | - | - | - | - | - | - |
| Organisation | - | - | - | - | - | - | - | - | - | - |
| Group | - | - | - | - | - | - | - | - | - | - |
| Position | - | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | - |
| Person | - | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | - |
| Project Team | - | - | - | - | - | - | - | - | - | - |
| Committee | - | - | - | - | - | - | - | - | - | - |
| Venue | - | - | - | - | - | - | - | - | - | - |
| Workgroup | - | - | - | - | - | - | - | - | - | - |
| Storage Provider | - | - | - | - | - | - | - | - | - | - |
For every delegating Location type in the left column, you can see the possible Location types that can be delegates under Delegates.
| Delegating | Delegates | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Unknown | Organisation | Group | Position | Person | Project Team | Committee | Venue | Workgroup | Storage Provider | |
| Unknown | - | - | - | - | - | - | - | - | - | - |
| Organisation | - | - | - | - | - | - | - | - | - | - |
| Group | - | - | - | - | - | - | - | - | - | - |
| Position | - | - | - | Yes | Yes | - | - | - | - | - |
| Person | - | - | - | Yes | Yes | - | - | - | - | - |
| Project Team | - | - | - | - | - | - | - | - | - | - |
| Committee | - | - | - | - | - | - | - | - | - | - |
| Venue | - | - | - | - | - | - | - | - | - | - |
| Workgroup | - | - | - | - | - | - | - | - | - | - |
| Storage Provider | - | - | - | - | - | - | - | - | - | - |
- The electronic address type Signature can only be extracted for use by the person it is attached to, or any of that person's delegates
- A delegate of a Location with Can Complete Action and Can Complete Workflow Activity can complete Actions or Workflows on their behalf
For every administrator Location type in the left column, you can see the possible Location types they can administer under Administered.
IMPORTANT: Only Locations that have an active login can be an Administrator.
| Administrator | Administered | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Unknown | Organisation | Group | Position | Person | Project Team | Committee | Venue | Workgroup | Storage Provider | |
| Unknown | - | - | - | - | - | - | - | - | - | - |
| Organisation | - | Yes | Yes | Yes |
- |
Yes | Yes | Yes | Yes | Yes |
| Group | - | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes | Yes |
| Position | - | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes | Yes |
| Person | - | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes | Yes |
| Project Team | - | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes | Yes |
| Committee | - | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes | Yes |
| Venue | - | - | - | - | - | - | - | - | - | - |
| Workgroup | - | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes | Yes |
| Storage Provider | - | - | - | - | - | - | - | - | - | - |
- Content Manager applies purpose related KwikSelect search filters only to the initial selection of matching Locations.
For example, when you click KwikSelect to select a Location to be the Supervisor of an Organisation, Content Manager uses filters to display only Locations of Person or Position Location types because these are the only ones that could be a supervisor.
However, when you expand any of the initially displayed Locations to show their child relationships, Content Manager does not apply this filter.Similarly, when you enter a prefix within the list box and you use the Jump command, Content Manager does not apply the filters. See Location Jump.
Content Manager checks the validity of the Location when you select one or more Locations to proceed with.
- You can set the filter Show Locations without 'Can Use' access by right-clicking the search result and on the Search menu, clicking Refine Search and selecting it on the Filter tab.
If it is not selected, Content Manager will only show Locations that have Can Use access.
Generally, when selecting a Location for a particular purpose - for example, as an Assignee - any Location type is valid except Unknown.
The exceptions to this rule are:
- When the purpose is creating a relationship with another Location - rules above
- An email message may be sent to an Unknown Location type
- A record Contact can be an Unknown Location type
The Location types in the left column and some of their possible permissions and functions.
| Type | Can Have Security Profile | Can Have Login | Can Own Labels | Can Be Flagged For Stats | Can Be External | Can Have A Duplicate Name | Can be Assignee or Home of a record | Can approve agenda items, to do assignee, workflow supervisor, be search owner, have access control |
|---|---|---|---|---|---|---|---|---|
| Unknown | - | - | - | - | - | - | - | - |
| Organisation | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Group | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes |
| Position | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes |
| Person | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes |
| Project Team | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes |
| Committee | Yes | Yes | Yes | - | Yes | Yes | Yes | Yes |
| Venue | Yes | Yes | Yes | - | Yes | Yes | - | - |
| Workgroup | Yes | Yes | Yes | - | - | Yes | Yes | Yes |
| Storage Provider | Yes | Yes | Yes | Yes | Yes | Yes | Yes | - |
- Only users with Can Modify External Locations or Can Modify Internal Locations permission can make changes to the Location relationship structure
- Only users with Modify Logins and User Profiles permission can access or change data in the Profile tab.
See Profile page.
- Records that are contained and enclosed in their containers are At Home in their container. As a result, the Home field of the contained and enclosed record indicates that it is in a container and display the container number.