You can configure a package (which is a single server process) to run as one of the following package identities:
By default, MTS packages run as Interactive User.
In many deployment scenarios, it is preferable to run a package as an Windows NT user account. If a package runs as a single Windows NT user account, you can configure database access for that account rather than for every client that uses the package. Permitting access to accounts rather than individual clients improves the scalability of your application.
For example, consider an Accounting package that updates a SQL Server database with billing and sales information. You can configure the database Accounting table to allow read access for users in the Windows NT accounting clerk group account. You can then set the package identity to the accounting clerk group account, which allows members of that account to run the package and read data from the Accounting table.
Note that if you want to use package identity to restrict access to a database, you must set database access privileges for the user account.
See Also
Mapping MTS Roles to Users and Groups, Enabling MTS Package Security, Adding a New MTS Role, Identity Tab (Package)