The user access is quite straightforward, the user are linked to a personal email for regulatory purposes (electronic signature compliance with Part 11 and such). We can have R/W users (can be admin or not) to at least one project or globally Read-Only users.
Example: if you have USER A, B and C as Read/Write access and USER D and E as Read-only:
User A, B and C can change everything they want (in the selected project they have access to)
User D and E can read, download document and even sign documents.
More info on user access here: User access
As guest option you can invite any external user by creating an account and having her/him as Read-Only (like an auditor). This user won’t be able to fill in test forms or comment some reviews (for that (s)he needs editing rights). See How can I give external people access to my project?
But, what you can always do is this: during a test period where USER D and E need to be involved, you can adapt the access and put:
User A, D and E with R/W access
User B and C you change them to Read-Only access so that the monthly invoice is not changing (you still have 3 R/W licenses and 2 R-O licenses in total).
So, in short:
Admin and R/W user to at least one project will pay a R/W license (admin will have access to the administration part of the SW to configure, manage users etc.. no extra cost for that)
Read-Only users can read, download and sign documents (and even perform trainings on the LiveQMS)
For QMS project, there is another access, it’s the Q access. This access is even more limited than the Read-Only access as it provides access to the published QMS only (LiveQMS platform) without providing access to the Matrix project at all but can perform its training. Very good for an external auditor for example as well to access only the approved versions of your procedures and everything you published.
PS: if you want to restrict the R/W access for some users allowing them to only edit certain part of the project (only the TC and execution, not the other design element for example), you can use an extra module called User access limitations. This module allow you to specifically provide write restrictions for group of user(s) within a project. More info on User access limitation
If you’re using group of users, you can also manage the access to different project with the group of users (to be more efficient than doing it per user). The highest access provided via the group or the single user will determine the final access to the project. More info on Group Access to Projects .