Maintaining the User Directory for Workflow Applications

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

For a user to be able to access your workflow application, you must add the user to your workflow application even if the user will not be writing to the database. You might want to have a user in the directory but not make it possible for them to see or modify data, in which case you can add them to a role that has no permissions on any database objects.

To keep the user directory current, the administrator designates a synchronization schedule. The user directory can be scheduled to synchronize on a regular basis to update the modUserList table with information for all of the users who have access to workflow applications.

Users in the User Directory

To have access to your applications, a user must be listed in the User Directory or be part of a group listed in the directory on the server or named instance that manages the workflow application.

**Note   **If you are using SQL Server Named Instances on your server, you must install the Workflow Services for SQL Server on each named instance. The Workflow Manager for SQL Server provided with the services only manages a single server or instance of a server at a time.

See Also

User Information for Workflow Applications | Synchronizing the User Directory | Populating Controls with User Information