When designing the security model, there are three methods depending on the solution. For ISV solutions, the security should be designed into the main package and shipped together. This also goes for partner solutions for new customer implementations when the package is a discreet package of functionality. Sometimes, customers need roles customized for their own needs, and these roles may encompass privileges for both new and existing functionalities. In this case, a new package should be developed. Having a separate package also aids work planning efficiency.
Should the end user customer develop their own security model, this should always be in a new package; although, the same functionality can be achieved within the application.
The security model in Operations is broken down into the following structure:
- Roles
- Duties
- Privileges
- Policies
The primary structure of the security model includes Process...
