Hi Rob,

If you need to create and update projects dynamically within your application, I think your approach to create a Project/Role/User table makes sense since they provide a project-level control that you wouldn't be able to get from built-in OutSystems User roles, and you can easily query that Entity for validating user permissions and create/delete records to grant or revoke them.

In general, calling Server Actions or other potentially slow actions in the OnInitialize event handler will slow down your application and therefore it is not recommended because it runs in full before the user navigates and renders the screen. For checking the role, you should instead create a Data Action and call your Server Action from it, including one or several output parameters to represent the access levels. After this, you can modify the logic/appearance of your screen to adapt according to these values.

Now, for granting the permissions, the user shouldn't be granted permissions automatically just by entering a screen. I would recommend having some other direct mechanism, say a separate "Control Panel" screen where an App Administrator type of role can assign and check permissions to different users and projects. If for some reason you need a 'default' role for all users entering all types of screen projects, then you could use the absence of a record in your ProjectId/RoleId/UserId table to represent that default role, so that you don't need to create new records unnecessarily every time a user enters a project screen.