This is quite configurable, but there are 4 main steps, or actually roles, available: Authors, Reviewers, Approvers and QA persons.
The drafting of the document is done by one or more authors. Once the document is pushed to the review status, one or more reviewers need to review it. Reviewers can still edit the document, so after the review step, if Scilife detects that changes were made by a reviewer, authors need to sign off on it later again.
After the review step, the document goes into the next status which requires one or more approvers to review and approve the document. Approvers cannot edit the document anymore.
Once approvers have signed off, one or more QA persons need to sign off too, after which the document can be published immediately or at some point in the future.
Of course! The system offers the possibility to define authors, reviewers, approvers and QA people for sign off purposes, but you can leave out reviewers or approvers for example. You can do that on document level or you can completely deactivate a step in the module configuration.
We have implemented an integration with Microsoft Office. So you can use your trusted MS Word, Excel or Powerpoint applications to edit documents, which are then automatically saved in the Scilife cloud upon clicking save in your desktop application.
Absolutely. We call these Document Types. A Document Type could be a standard operating procedure, or a work instruction, for example. For that document type, you can then upload a file as a template which is then automatically copied when you create a new document.
There are 4 types of users in Scilife: Administrators, Managers, Regular Users and Read-Only Users. The first 3 can create, edit and participate in the review and approval workflows. Read-Only Users can obviously read documents and also mark them as Read&Understood.
The AD/LDAP integration is meant for companies who use Microsoft Active Directory to manage employee access to software systems in a centralized way.
This way, employees only need one user ID and password to login into many of the software systems at their company.
With Single Sign On (SSO), the user doesn't even need to provide their user ID and password every time. As they are logged in to their PC, their credentials are automatically passed on to the system they want to access, logging them in instantly without showing a login page.
Scilife has an integration with Microsoft AD over the LDAP protocol to provide exactly this functionality.
Additionally, when users in Scilife need to sign off on a document with their electronic signature (normally their Scilife login+password) they can use their Active Directory ID and password.
All data in Scilife is encrypted at all times, both in transit (between your browser and the platform) and at rest (when data is stored).
Scilife runs in the Amazon AWS cloud, which is still considered the best cloud infrastructure provider according toGartner’s magic quadrantand complies according to a plethora of regulations. We encourage you totake a look at it here.
Each client gets their own separate database. Actually, better yet: each client gets 3 different environments (TEST, VAL, and PROD), and each with their own database. In other words, data from different clients is never sitting in the same database.
The Scilife platform runs in a VPC (virtual private cloud), which effectively separates it from the rest of Amazon AWS's client's data. In the VPC, it is divided into a 3-tier system: application servers, database servers and file storage are separated, which makes it easier to scale out automatically when demand increases and therefore ensures a speedy user-experience.
Besides the standard automated backups of client data, we use many different Amazon AWS services to ensure data integrity, application reliability and to have robust disaster recovery mechanisms in place.
Data security and data integrity are aspects that we take very seriously, as we are aware that your business depends on it. And ours too!
Yes, with the Groups functionality you can configure which users have access to which documents.
Users can have access to one or more groups and documents are always placed at least in one group. Therefore, the rule is simply that a user must have access to at least one of the document's groups in order to see the document or gain access to it.
Yes, but only for the following file types: docx, xlsx, pptx and pdf.
It depends on the system you are currently using and on the number of documents you need to migrate. If you only have tens of documents you could use the document import feature to import your documents one by one. But if you have more, we can help you to automate the process by developing an import script. Depending on the complexity of your data, we might need to charge you the development hours of this script, but it will save you loads of time.
Scilife handles the versioning of documents for you. When you create a new document, it starts at version 0.1. While editing the document, Scilife will save these as 0.2, 0.3, 0.4 etc. Once the document is finished, approved and published, it is published as version 1.0. When the document is later reviewed, the version is increased automatically again to 1.1, 1.2, 1.3, etc. until you publish it as 2.0 again. All intermediate document versions are saved and can be consulted depending on your permission role.
Yes, there are 4 types of users in Scilife: Administrators, Managers, Regular Users, and Read-Only Users. The first 3 user types can edit and participate in the approval workflow, the Read-Only User type can only read documents and mark them as Read&Understood.
