Defining Permissions for Offline Publications

See Also

Users create a subscription to an offline publication, which creates a local copy of the database and the Web site, so they can work offline. Each publication has a Publications Access List (PAL). By adding roles to this list, you define who has the ability to take the publication offline. Anyone who belongs to a role that is listed has full access to the publication when it is offline.

Security is enforced during the synchronization process when the user goes back online—not while offline. Although the offline user has database owner access to the local database and can make any changes, when the user goes back online, the server database security rules are enforced during synchronization. Security is maintained through database roles assigned in the Access Workflow Designer. For information about adding users to roles, see Assigning Users to Database Roles.

Important   If a new user is added to a role with permissions to access a publication, someone with database owner permissions must update the PAL to make it possible for the user to have immediate access to the publication. To update the PAL in the Access Workflow Designer, from the Tools menu, select Update Publication Access Lists.

You can change the permissions for the offline publication based on the roles in your solution.

To set offline permissions

  1. Open your solution in the Access Workflow Designer. For details, see Opening your Solution in the Access Workflow Designer.

  2. In the Object List, expand Offline Publications by clicking the plus (+) sign.

  3. Select an offline publication from the list to display the Offline Publication panes.

  4. In the Offline Publication pane, select the Permissions tab.

  5. Select the box next to any roles you want to make available to work offline. For roles you want to restrict from working offline, clear the box.

  6. Select Re-create SQL Publication. When prompted to save, click Yes.

In the Workflow Process pane, you can specify which workflow actions are available offline. This gives additional security and can keep certain types of actions from occurring offline—for example, timeout events that send mail must be disabled when offline. For details, see Adding and Modifying Actions for States.

For an example of how to implement offline support, see Offline Support in the Issue Tracking Solution.