Permissions and access

There are two built-in permission sets for this area:

• Sifterra - Read
• Sifterra - Full

Use Sifterra - Read For Review Access

Use Sifterra - Read for people who only need to:

• view setup
• view analyzers
• review queue entries
• inspect extracted data, logs, and results

This is the right default for most reviewers, managers, and department users who need visibility but should not change setup.

Use Sifterra - Full For Administrators

Use Sifterra - Full only for people who need to:

• change setup
• create, copy, or delete analyzers
• change field mappings and matching rules
• retry failed items
• create documents from reviewed entries

With full access, a user can change setup, change analyzer behavior, delete analyzers, delete queue records, and change automation settings. That is broader than most reviewers or department users need.

Permission Review Practices

Good practice:

• default users to Sifterra - Read
• grant Sifterra - Full to a very small admin group
• review full-access assignments regularly
• remove full access when temporary setup work is complete

Also remember that document processing can create or update records elsewhere in the system. Access to this area alone does not replace the need for appropriate permissions in the target business areas.

Current Permission Model Limits

The built-in security model offers only:

• Sifterra - Read
• Sifterra - Full

What this means:

• there is no built-in role for users who should manage exceptions or retries without also being able to change setup and delete records
• if your process needs that separation, you may need a custom permission design

When Access Questions Become Setup Questions

If a user needs broader automation changes, analyzer redesign, or changes that affect how records are created, treat that as an administrative or implementation decision rather than a routine access request.

For the related change controls, see Maintenance and escalation.