Workspaces offer a customized view of the platform. They aggregate specific rules and permissions based on customer needs.
A user can have multiple workspaces and for each of them a different role.
A workspace can be related to a single client.
Peter is an accountant and owns a small accounting company "Awesome accounts LTD". Both his company and his client "We build LTD" are clients of the platform.
Awesome accounts LTD has a single workspace which gives Peter full access. He can create and view documents for the company.
We build LTD has two workspaces.
One setup for full access - employees of We build LTD are assigned to this workspace. They can create and list documents.
One that allows only
read access to the inbox and sent documents - Peter as accountant of We build LTD is assigned to this workspace. He can only view the documents, download the presentations, but he cannot create.
Once Peter's contract ends, he can be removed from the accounting workspace and will no longer have access to the documents of We build LTD.
Pipelines at their core are document flows. They are incredibly flexible and can match the most complex of business requirements. A client can have one or more pipelines based on their business requirements.
A basic example
We build LTD has two pipelines:
One for archiving purposes - the requirement is simple: all documents issued to this pipeline need to be stored on the platform, nothing more
One for sending documents to it's partners - the requirement is more complex: all documents issued to this pipeline need to have some validations, pdf's must be created and sent via email
Documents are transactions on the platform. They are differentiated by type. Commonly used document types are
Credit notes etc.
Steps are actions executed by the platform for each document. An example of commonly used step is creating a pdf presentation. Steps are part of pipeline configuration.