First Configuration Steps

To get started with Rossum, you will want to configure your account according to your needs.

User Accounts

We call your whole Rossum account an organization, where multiple individual user accounts may have access. You will want to add a user account for every individual accessing your organization, whether to do the actual data capture or administer the account.


The documents processed within your Rossum organization are flowing in queues, transitioning through various states. You may configure each queue to capture different data, have different user accounts associated, and allow separate data export. Queues may be logically grouped in workspaces for ease of orientation.

You will want to go beyond your single queue if you need to separate your documents into multiple streams. You may need to capture different information from various document types or have multiple teams working on documents, or just because of how your business process is set up.


Moving to production

Having a separate testing and production queue is a good idea. Suppose you are confirming documents in a queue without validating the captured data properly. That may confuse the AI and reduce the automation rate until the AI "unlearns" its mistakes again, which may take quite a while. Since AI learning is confined to specific queues, handing the account over from developers to the data capture team may be a good moment to clean the history for AI's sake.


The particular structure of the captured data is described in a schema. Basic tweaks of the fields to capture can be done in the Field settings section. You can add and remove extra standard fields to capture everything you need and save time on optional fields. You can do more advanced tweaks in the Schema Editor - adding custom fields and sections, controlling required and default values, or tweaking automation levels.

Configuration Tools

The easiest way to update the above is in the Settings section of the Rossum app. Sometimes, applying lower-level access to the API is useful. It may be helpful, e.g., when scripting around some operations - you will want to use our command-line configuration tool rossum.