Team Default Permissions For New Items View
Team default permissions for new items allow you to specify explicit permissions for other teams that will be assigned to new items you create. This allows you to restrict, or enhance, permissions a team has to records you create over and above their default permissions themselves.
Team Default Permissions For New Items Features
It is often the case that you want teams to have access to certain sets of information, and other teams to have access to different sets of the same type of information. Normally this would require you to explicitly set permissions when creating every new item. Instead this functionality is designed to automatically assign explicit permissions to different teams whenever you create new items.
For any given Default Permission, you can assign permissions that other teams (including overriding permissions for this team itself) will be explicitly given when you create an entity of that type.
You don't need to give the team default permissions of "Can Change Permissions" to that entity in order to define this behaviour.
You can override the current teams permissions to provide it different permissions for items it creates versus those created by others. For instance its default permissions maybe None, and Create. This way by default it can not see any other items created by other teams, however when it creates one the permissions can be overridden to provide it read/write permissions for items this team creates only.
This allows you to solve very common scenarios in an easy and automated fashion. For instance if you have Accounting Team A, and Accounting Team B, both with default permissions of create/write/read to transactions this allows you to ensure they work on different transaction records and can't alter the other teams. For Team A you can setup default permissions for new items for the Transactions entity type that assign Team B no permissions to write and only permissions to read. Vice-versa for Team B. This means whenever Team A creates a transaction Team B is automatically explicitly given permissions to only be able to read that transaction and not write to it as its default permissions allow.
This advanced functionality easily and efficiently allows you to setup teams that can work according to how your business compliance, rules, and regulations require.
Team Default Permissions For New Items Properties
Team default permissions for new items have the following properties:
| Name | Description |
| [Key] [Required] Team | The team that you want to provide different explicit permissions to whenever this team creates new instances of this entity type. |
| Can Read | Indicates this team has permissions to read this newly created record. If they do not have this permission, the team will never be able to see this record through any function of the system be that the API, web services, reports, applications, etc. |
| Can Write | Indicates this team has permissions to alter this newly created record. If they do not have this permission, the team will never be able to change this record through any function of the system be that the API, web services, applications, etc. |
| Can Delete | Indicates this team has permissions to delete this newly created record. If they do not have this permission, the team will never be able to delete this record through any function of the system be that the API, web services, applications, etc. |
| Can Change Permissions | Indicates this team has permissions to change permissions on this newly created record. If they do not have this permission, the team will never be able to alter permissions on this record through any function of the system be that the API, web services, applications, etc. |
Can Create isn't a permission that exists here as the record has already been created - you are explicitly setting permissions for a newly created record for the specified team.
Commands
A team default permissions for new items has the standard set of commands and functions when being viewed from a grid. See our standard grid functionality.