When users connect to a team solution, the activities they can perform are determined by the permissions granted to their security accounts, Windows NT groups, or role hierarchies to which their security accounts belong. The user must have the appropriate permissions to perform any activity that involves changing the database definition or accessing data. Some activities, such as those that do not change items in the database or access data, do not require permissions.
There are six permissions you can grant to a role in SQL Server: Select, Insert, Update, Delete, Execute, and DRI (declarative referential integrity). For more information about these permissions, see the SQL Server Books Online.
When you identify a database table as a main table using the Main Table Selection wizard, Access Workflow Designer assigns permissions to the Public role for the base table and creates a view called <tablename>view that makes it possible for data access pages to function. The permissions include Select on the primary key, Insert, and Delete. A user must have these permissions for data access pages to work correctly. These permissions are assigned to the Public role, so by default, all team solution users have them.
Note When you view the role permissions, it appears as if there are Select permissions on the entire table, when in fact, the Select permissions are on the primary key only. If you manually remove and add Select permissions, then you are granting Select permissions on the entire table. This, however, disables row-level permissions.
If you do not want all users to be able to take a solution offline, you are not required to revoke permissions for the Public role. You can set Offline Publication permissions using the Access Workflow Designer and designate which roles can take a solution offline. For details, see Defining Permissions for Offline Publications.
You can add Update permissions for a particular role if you want to make it possible for users in that role to change information. Assign Update permissions to the Public role if you want all users to have this ability.
To assign role permissions
Note When your team solution is open in the Access Workflow Designer, you can access the Security option from the Tools menu in the designer.
Important A user must have Select on the primary key, Insert, and Delete permissions to perform update actions when a team solution is taken offline.
Note If using row-level permissions for a table, you cannot grant Select permissions on the entire table. You must grant Select permissions only to the primary key column. Therefore, you must use a stored procedure to grant column permissions (permissions on a single column rather than an entire table).