No, you don't have to distribute the security projects... the security data is designed so that only one project's data is deployed to a server at a time.  Each project is supposed to be a "development" project, meaning an application.  So, if you have different administrators for different areas of an application, you create a separate role for each section's administrators.  But the data for 2 different projects should not be deployed at the same time.

In the Security Maintenance program there doesn’t appear to be any way to restrict access to projects within a database. So if you have multiple applications/security projects and wanted to limit a “security administrator” to a specific application you would need to include the security project tables for that application in its own database or the application database.  Am I correct or missing something

 

-Larry