We will execute a mutual non-disclosure agreement on request, or if you wish to discuss Provable Correctness.
A Consultant company in Chemintro is one with at least one user in the the Consultant role. The Consultant role is available on request.
A new company may be registered in Chemintro by an already logged-in user. If that user is in the Consultant role the new company will become a Client company..
Users with the Consultant role can see a list of their Client companies when logged into their own company.
A Consultant must have a Client company login to see Client data. See 'Silo' below.
ONE SILO PER CLIENT
Each company registered in Chemintro is a secure information silo.
Within a company, there can be multiple named 'Divisions' each of which would have one AICIS Portfolio ID.
From an information management perspective, this allows chemicals from multiple portfolios to be ingredients in the same company products.
UNIQUE USERNAME PER CLIENT
The ideal username incorporates the company abbreviation or acronym. For example, mike@abc might be Mike's username for logging into ABC Pty Ltd.
This puts 'Mike(ABC)' at the top of every Chemintro page while working on ABC Pty Ltd. This helps with managing interruptions during a typical working day.
Occasionally, different consulting companies work for the same client company. Chemintro still handles this in separate, secure silos. Contact us to discuss options.
Best security practice has permissions for roles which are assigned only as required.
The most sensitive role is Admin. If you register a company in Chemintro, you automatically acquire the Admin role.
Only the Admin user can see all other users for a company. Only the Admin user can assign/remove roles and add/disable user logins.
This makes the Admin role effectively responsible for security. Consultants should therefore retain the Admin role exclusively for themselves.
If a new Client comes on board with an existing Chemintro account, requirements for keeping secrets are:
- Agree with the Client exactly who is responsible for security
- The agreed responsible person should exclusively acquire the Admin role
- The Admin should prune non-essential roles from all users
- The Admin should disable login for all non-current users
Although counter-intuitive, the operational Admin user should create a backup or standby Admin username with an appropriate email address in case Admin access is required in an emergency. The person with the nominated email address will be able to reset that password and login as Admin if required.
If a Client wishes to see/edit their own chemical or product information, only the Author role is required.
The Manager role can be assigned to a Client user to show Chemintro billing of the Client company or payments made by the Client. This role also permits editing corporate information.
The Admin role should not be assigned to Client users - unless the Consultant is willing to share responsibility for security.