You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the platformAdmin role is limited to CRUD RegulatorAdmin (and other PlatformAdmin). But we can expect that all the RegulatorAdmin(s) and RegulatorUser(s) will have (at least for the first months after onboarding) limited experience and could need some help to correct errors (like users without affiliation, etc.)
The simple way to solve that is to allow the PlatformAdmin to CRUD all "regulations", "regulators", "sectors" (like now), but also "companies" and "users", including the affiliation of users to companies or regulators + "admin" role, but excluding mix of both.
There should be no access to incidents for the PlatformAdmin.
At this moment, the users created by the PlatformAdmin have no association atall, hence theses users can login, but are "outside the protocol" and can't do anything useful. Correcting this and other errors shouldn't imply a manual modification in the database !
The text was updated successfully, but these errors were encountered:
At the moment, the platformAdmin role is limited to CRUD RegulatorAdmin (and other PlatformAdmin). But we can expect that all the RegulatorAdmin(s) and RegulatorUser(s) will have (at least for the first months after onboarding) limited experience and could need some help to correct errors (like users without affiliation, etc.)
The simple way to solve that is to allow the PlatformAdmin to CRUD all "regulations", "regulators", "sectors" (like now), but also "companies" and "users", including the affiliation of users to companies or regulators + "admin" role, but excluding mix of both.
There should be no access to incidents for the PlatformAdmin.
At this moment, the users created by the PlatformAdmin have no association atall, hence theses users can login, but are "outside the protocol" and can't do anything useful. Correcting this and other errors shouldn't imply a manual modification in the database !
The text was updated successfully, but these errors were encountered: