When adding people to a project, some members may need to have different roles applied to them or specific needs for permissions, depending on the project. If notes could be added at the account level, an account admin could add a reminder in that note for any specific individual needs for a user. This would allow for a base role to be applied at the account level and would give notice to project admins when adding members for those specific needs. Depending on how it would be used, you could create a semi-role hierarchy at the individual member level.
An example for this would be a role hierarchy for folders in the files module, for groups like external users, using roles. At the project template level, you could create a top-level folder for all external users that would contain any useful information or training that may be needed for all to view, using a role that is applied to all external users at the account level for basic viewing permissions. A sub-folder can then be created for the specific role an external user would have like if they are a vendor or sub-contractor. You may have specific document upload requirements for vendors that wouldn't apply to sub-contractors. Then at the project level a project admin would add the external users and check to see if they need to apply any additional roles or permissions in the project; based on notes from the account level. Then they can add company specific folders if the specific role-based folder does not cover everything. Such as if you have multiple vendors supplying the same equipment and want to organize their document submission. By planning to set multiple roles you can move having to set permissions in many different folders to just folders for members from specific companies.
Top Level Folder for All External Users (Project Template Level)
> Specific Role Based Folder (Project Template Level)
> Specific Company folder if needed (Individual Project Level)
This would eliminate the need to track these different needs in an external program.
