<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Ideas for Parashift</title>
  <subtitle>Ideas for Parashift as submitted to our Feature Upvote board. Ideas are ordered by 'new' and the 50 top matches are included.</subtitle>
  <link href="https://feedback.parashift.io"/>
  <id>pr_oh2s0pbfmgiimvw</id>
  <updated>2026-04-22T06:07:57Z</updated>
  <entry>
    <title>Notification - API key expiration</title>
    <link href="https://feedback.parashift.io/suggestions/695649/notification-api-key-expiration"/>
    <id>sug_gxgt85ck9d1j6ax</id>
    <published>2026-02-19T13:11:41Z</published>
    <updated>2026-04-22T06:06:18Z</updated>
    <content type="text/plain">A new API Key is valid for 6 month.&#13;
I would like to have a notification, before an API Key is expiring, so there will be no interuption for the customer just because we did't remarked it.</content>
  </entry>
  <entry>
    <title>Use roles / groups to edit user permissions</title>
    <link href="https://feedback.parashift.io/suggestions/702843/use-roles-groups-to-edit-user-permissions"/>
    <id>sug_fkgtai9zj5mfw7p</id>
    <published>2026-03-24T14:43:06Z</published>
    <updated>2026-04-22T06:06:16Z</updated>
    <content type="text/plain">Today we need to edit each users permissions individually. It would make editing permissions a lot easier if you could use groups to edit many users at once. Even better if you could push these permissions between tenants.</content>
  </entry>
  <entry>
    <title>Copy and duplicate all fields</title>
    <link href="https://feedback.parashift.io/suggestions/704122/copy-and-duplicate-all-fields"/>
    <id>sug_wn2untgymnhgojs</id>
    <published>2026-03-31T15:48:29Z</published>
    <updated>2026-04-22T06:06:13Z</updated>
    <content type="text/plain">Sometimes I need to create a new doctype that is variation of a similar existing document type. If I copy the existing one, both are using the same fields. Although I don't want any shared element between those 2 doctypes. I'd love to have a "Copy with new fields" option</content>
  </entry>
  <entry>
    <title>Markieren der Werte pro Zeichen, z.B. mit Pfeiltasten</title>
    <link href="https://feedback.parashift.io/suggestions/693537/markieren-der-werte-pro-zeichen-zb-mit-pfeiltasten"/>
    <id>sug_kwdqnqr971gsluh</id>
    <published>2026-02-09T08:30:23Z</published>
    <updated>2026-02-10T05:31:16Z</updated>
    <content type="text/plain">Es wäre hilfreich, wenn man für das Training die einzelnen Werte je Feld auf Zeichenebene, z.B. mithilfe der Pfeiltasten markieren könnte. Ist so etwas vorgesehen?</content>
  </entry>
  <entry>
    <title>Sort list of tenants in alphabetical order (by default)</title>
    <link href="https://feedback.parashift.io/suggestions/692540/sort-list-of-tenants-in-alphabetical-order-by-default"/>
    <id>sug_plkre3ueizzvhlg</id>
    <published>2026-02-03T12:41:40Z</published>
    <updated>2026-02-10T05:31:02Z</updated>
    <content type="text/plain">For admins who are active in many tenants, the list is long and not sorted. Having it sort in alphabetical order would make the list more clear and easier to find a certain tenant. This would be the easiest improvement to implement, I think. Another idea is to be able to make certain tenants "invisible" in the "Personal settings" page, so it would not show in the quick list. Ofcourse users should be able to undo this too and make tenants visible again.</content>
  </entry>
  <entry>
    <title>PDF resolution: inbound differ on outbound</title>
    <link href="https://feedback.parashift.io/suggestions/689975/pdf-resolution-inbound-differ-on-outbound"/>
    <id>sug_rdnuv1psmioaybj</id>
    <published>2026-01-20T07:20:38Z</published>
    <updated>2026-02-10T05:30:34Z</updated>
    <content type="text/plain">Hey there&#13;
&#13;
The resolution of the outbound PDF are differ from the resolutuion of the inbound.&#13;
The problem is that parashift turns the pdf to an image and it will converted in an image with 2500 pixel longest side.&#13;
If you have set the checkox "Generate Output PDF" in the upoad-config it must be so, that the inbound resolution is the same as the outbound, for example 300dpi.&#13;
&#13;
Actually this differ and when the result of some docments before and some documents from parashift merge you got an PDF with different page sizes.&#13;
&#13;
&#13;
Thanks &amp; Best regards</content>
  </entry>
  <entry>
    <title>Tenant search non-case-sensitive</title>
    <link href="https://feedback.parashift.io/suggestions/679482/tenant-search-noncasesensitive"/>
    <id>sug_u7btds7jfkfhbh9</id>
    <published>2025-11-26T08:55:31Z</published>
    <updated>2026-02-10T05:30:15Z</updated>
    <content type="text/plain">The tenant search in the menu over "Powered by Parashift" is only case-sensitve. It would be nice to search non-case-sensitive.</content>
  </entry>
  <entry>
    <title>Field Config: Hide in EV</title>
    <link href="https://feedback.parashift.io/suggestions/674351/field-config-hide-in-ev"/>
    <id>sug_bhtnlwr9eer8xn2</id>
    <published>2025-10-28T12:53:33Z</published>
    <updated>2025-11-12T05:49:03Z</updated>
    <content type="text/plain">To keep the EV view clean, for example, if  not the training option or not for validation is active, the "hide" field should be available.</content>
  </entry>
  <entry>
    <title>Add more API Request</title>
    <link href="https://feedback.parashift.io/suggestions/673356/add-more-api-request"/>
    <id>sug_vxi7vciuslcybgd</id>
    <published>2025-10-22T11:21:19Z</published>
    <updated>2025-11-12T05:55:09Z</updated>
    <content type="text/plain">- separation-validation via API&#13;
- remove/add batches to training</content>
  </entry>
  <entry>
    <title>learning data only learn downward</title>
    <link href="https://feedback.parashift.io/suggestions/658561/learning-data-only-learn-downward"/>
    <id>sug_kf7k4jtkmssevpi</id>
    <published>2025-08-04T13:01:24Z</published>
    <updated>2025-11-12T05:55:17Z</updated>
    <content type="text/plain">It would be a useful feature if there were an option to pass data up or down from the tenant's perspective. For example, the tenant could only learn from its parent, but the learning data of this tenant would only be available there and would not be passed up to the parent and distributed to other children.</content>
  </entry>
  <entry>
    <title>QC for poor receipts | QC für schlechte Belege</title>
    <link href="https://feedback.parashift.io/suggestions/658548/qc-for-poor-receipts-qc-fur-schlechte-belege"/>
    <id>sug_ozggbzyixsldxxs</id>
    <published>2025-08-04T12:02:23Z</published>
    <updated>2025-11-12T05:49:30Z</updated>
    <content type="text/plain">Is there a way to ensure that only documents that have been poorly recognized end up in QC, while the documents still go through?&#13;
&#13;
The background to this is that some documents were not recognized properly in one of our child  tenant and now need to be manually trained.&#13;
&#13;
We would therefore like to have a filter that allows us to identify which documents were recognized below a certain value.&#13;
&#13;
Despite this, the documents should still be processed and the JobRouter processes should not prevent them from being processed.&#13;
&#13;
Filtering allows the customer to dive right into Parashift and train these documents.</content>
  </entry>
  <entry>
    <title>Restrict user permission to delete documents</title>
    <link href="https://feedback.parashift.io/suggestions/657309/restrict-user-permission-to-delete-documents"/>
    <id>sug_5cioicfpmnekosq</id>
    <published>2025-07-29T10:03:13Z</published>
    <updated>2025-11-12T05:55:28Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>Support regex pattern in Automatic Agent configuration</title>
    <link href="https://feedback.parashift.io/suggestions/652215/support-regex-pattern-in-automatic-agent-configuration"/>
    <id>sug_xypul9ugprso9jn</id>
    <published>2025-07-02T10:18:47Z</published>
    <updated>2025-11-12T05:55:34Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>Expose Services status via pubic API</title>
    <link href="https://feedback.parashift.io/suggestions/651980/expose-services-status-via-pubic-api"/>
    <id>sug_25q2gutyep8svrr</id>
    <published>2025-07-01T12:01:01Z</published>
    <updated>2025-11-12T05:56:17Z</updated>
    <content type="text/plain">potential value for: Healthcare Monitoring feature integration</content>
  </entry>
  <entry>
    <title>Make document viewer detachable for secondary screen use</title>
    <link href="https://feedback.parashift.io/suggestions/650385/make-document-viewer-detachable-for-secondary-screen-use"/>
    <id>sug_h1soje37vzbpfjv</id>
    <published>2025-06-24T14:22:05Z</published>
    <updated>2025-06-24T14:22:05Z</updated>
    <content type="text/plain">Users expressed a need for more screen space when working with both the document viewer and the validation form.</content>
  </entry>
  <entry>
    <title>Capture tokens from two different pages</title>
    <link href="https://feedback.parashift.io/suggestions/649206/capture-tokens-from-two-different-pages"/>
    <id>sug_g8avaudzz5txss3</id>
    <published>2025-06-18T14:51:39Z</published>
    <updated>2025-06-19T06:56:39Z</updated>
    <content type="text/plain">Capture tokens from two different pages is currently impossible.</content>
  </entry>
  <entry>
    <title>Model Versioning with Tenant-Specific Deployment Control</title>
    <link href="https://feedback.parashift.io/suggestions/638815/model-versioning-with-tenantspecific-deployment-control"/>
    <id>sug_yj9zzwj84ug9r3u</id>
    <published>2025-05-14T13:59:36Z</published>
    <updated>2025-11-12T05:57:44Z</updated>
    <content type="text/plain">"We understand that currently a single model version is used across all tenants for a given document type. To enhance flexibility and control, we propose implementing model versioning with the ability to manage deployment and usage of specific model versions per tenant.&#13;
&#13;
This feature would enable:&#13;
&#13;
- Targeted training and controlled rollouts&#13;
- The ability to rollback to previous model versions if needed&#13;
- Safe testing of new model versions in isolated environments&#13;
- Comparative analysis of model performance across versions to track improvements or regressions&#13;
&#13;
This would provide significantly more control and transparency in the model lifecycle and performance monitoring."</content>
  </entry>
  <entry>
    <title>Enable Read-Only Mode for Entire Tenant</title>
    <link href="https://feedback.parashift.io/suggestions/638813/enable-readonly-mode-for-entire-tenant"/>
    <id>sug_mukkeyzxswfi24s</id>
    <published>2025-05-14T13:58:07Z</published>
    <updated>2025-05-14T13:58:06Z</updated>
    <content type="text/plain">We aim to use shared tenants (e.g., dev, test, prod) that include all relevant document types. To maintain strict control over the training process, we would like these tenants to operate in read-only mode. Our existing training procedures are tightly managed and should remain the sole channel for model updates and modifications.&#13;
&#13;
Therefore, we request a feature that allows setting an entire tenant to read-only, ensuring that no new documents can be uploaded or used for training within that environment. This would help avoid confusion and prevent any unintended training activities.</content>
  </entry>
  <entry>
    <title>Parashift Platform Optimizing for Edge</title>
    <link href="https://feedback.parashift.io/suggestions/637940/parashift-platform-optimizing-for-edge"/>
    <id>sug_v769fw5txqkctvp</id>
    <published>2025-05-12T12:08:38Z</published>
    <updated>2025-05-12T12:11:57Z</updated>
    <content type="text/plain">According to assurance requirements, Edge is sometimes the preferred choice and Chrome is only made available by corporate IT departments in exceptional cases. In this respect, it would be helpful if the Parashift Platform was also offered optimized for the Edge browser in addition to Chrome. Overall, everything seems to work, but Chrome works a little better with larger workloads.</content>
  </entry>
  <entry>
    <title>Filter for manually processed documents</title>
    <link href="https://feedback.parashift.io/suggestions/630220/filter-for-manually-processed-documents"/>
    <id>sug_a0ktop5shnk2qn6</id>
    <published>2025-04-15T06:50:19Z</published>
    <updated>2025-05-12T12:11:58Z</updated>
    <content type="text/plain">Filter function to find documents that were manually validated during any workflow step.</content>
  </entry>
  <entry>
    <title>Fraud check for id documents</title>
    <link href="https://feedback.parashift.io/suggestions/621070/fraud-check-for-id-documents"/>
    <id>sug_d5vpfjyxludbfyk</id>
    <published>2025-03-13T08:58:02Z</published>
    <updated>2025-05-12T12:11:59Z</updated>
    <content type="text/plain">add a fraud tag to id documents if machine readable data and human readable data is not consistent.</content>
  </entry>
  <entry>
    <title>include document page count in JSON</title>
    <link href="https://feedback.parashift.io/suggestions/614030/include-document-page-count-in-json"/>
    <id>sug_oke8qsmu3i6c2qv</id>
    <published>2025-02-11T18:19:30Z</published>
    <updated>2025-05-12T12:12:00Z</updated>
    <content type="text/plain">Given that the page count is readily available, we would appreciate if it could also be included in the JSON output</content>
  </entry>
  <entry>
    <title>Customisation of the filter in the document overview</title>
    <link href="https://feedback.parashift.io/suggestions/612065/customisation-of-the-filter-in-the-document-overview"/>
    <id>sug_jmdhockfdmbqmet</id>
    <published>2025-02-03T09:16:30Z</published>
    <updated>2025-02-03T10:26:52Z</updated>
    <content type="text/plain">It would be great if the filter options in document overview could be customised and you could filter by vendor or invoice number, for example.</content>
  </entry>
  <entry>
    <title>Page 1 no longer rotates incorrectly for a multi-page document</title>
    <link href="https://feedback.parashift.io/suggestions/611478/page-1-no-longer-rotates-incorrectly-for-a-multipage-document"/>
    <id>sug_nctwcholvoeoboe</id>
    <published>2025-01-31T09:36:01Z</published>
    <updated>2025-11-12T05:57:33Z</updated>
    <content type="text/plain">In the case of a multi-page document, it occasionally happens that previously correct pages are rotated incorrectly when pages are rotated. &#13;
This must be switched off or be customisable.</content>
  </entry>
  <entry>
    <title>Update image-enhancement engine</title>
    <link href="https://feedback.parashift.io/suggestions/610873/update-imageenhancement-engine"/>
    <id>sug_vooizn1arzrmnvh</id>
    <published>2025-01-29T10:52:25Z</published>
    <updated>2025-02-03T10:27:09Z</updated>
    <content type="text/plain">Our engine with rotation document need to be updated...</content>
  </entry>
  <entry>
    <title>Standardizing the interpretation of data from right to left. (Hebrew)</title>
    <link href="https://feedback.parashift.io/suggestions/594413/standardizing-the-interpretation-of-data-from-right-to-left-hebrew"/>
    <id>sug_ttvamnmh9aclxew</id>
    <published>2024-11-18T14:54:16Z</published>
    <updated>2025-02-03T10:27:12Z</updated>
    <content type="text/plain">It is about standardizing the interpretation of data from right to left.&#13;
-	If you move the Hebrew words in the editor, the value is automatically rotated correctly.&#13;
&#13;
-	However, if the value is supplied via detection, the rotation does not take place.&#13;
	We now have the option of defining a transformer for each field 3 2 1 becomes 1 2 3&#13;
	However, this is not possible with line breaks, as can be seen in the example</content>
  </entry>
  <entry>
    <title>RAG system</title>
    <link href="https://feedback.parashift.io/suggestions/592507/rag-system"/>
    <id>sug_haub5yppcvv7z0e</id>
    <published>2024-11-08T13:19:05Z</published>
    <updated>2025-11-12T05:56:34Z</updated>
    <content type="text/plain">I have two customers who want to use a RAG system to use LLMs on a larger context.&#13;
&#13;
In both cases it is necessary to create multiple vector DBs that can be used dynamically in POST calls. One would like to be able to build these based on document types and tags, the other would like to create this either via a batch upload (at least 5-10 GB of files) or via document IDs that should be embedded.</content>
  </entry>
  <entry>
    <title>Simplification of webhook activation</title>
    <link href="https://feedback.parashift.io/suggestions/592465/simplification-of-webhook-activation"/>
    <id>sug_adqavtoitsllkhi</id>
    <published>2024-11-08T08:26:33Z</published>
    <updated>2025-11-12T05:57:07Z</updated>
    <content type="text/plain">Other services make it easier to understand what webhooks to activate when, for example, a user/system needs to follow-up with an intervention. E.g., "Activate all webhooks where intervention is required" and it automatically checks all relevant ones.</content>
  </entry>
  <entry>
    <title>Source/citation of information found by LLM</title>
    <link href="https://feedback.parashift.io/suggestions/591248/sourcecitation-of-information-found-by-llm"/>
    <id>sug_sm27qevwnjou7hc</id>
    <published>2024-11-01T07:56:05Z</published>
    <updated>2025-11-12T05:50:08Z</updated>
    <content type="text/plain">I want to be able to upload multiple files as context to an LLM (not as a batch) and receive info on where the LLM found information (document, page or section when, for example, the LLM provided a summary on specific parts of a document).</content>
  </entry>
  <entry>
    <title>POST possibility for LLM prompt</title>
    <link href="https://feedback.parashift.io/suggestions/591247/post-possibility-for-llm-prompt"/>
    <id>sug_hv9zg7zlj1sog7m</id>
    <published>2024-11-01T07:52:25Z</published>
    <updated>2025-11-12T05:50:26Z</updated>
    <content type="text/plain">In the context of a virtual data room use case, we would like to be able to send not only a document or a set of documents to the platform, but also an LLM prompt that is then applied.&#13;
&#13;
Use case: a prospective buyer looking at company data in the data room wants to get specific answers on a document or set of documents, or extract data such as contract clauses that they specify on the fly, and then compare those clauses across multiple contracts.</content>
  </entry>
  <entry>
    <title>Enable copying OCR text from the document view</title>
    <link href="https://feedback.parashift.io/suggestions/591069/enable-copying-ocr-text-from-the-document-view"/>
    <id>sug_hagpdrs7milekdm</id>
    <published>2024-10-31T12:04:14Z</published>
    <updated>2024-11-01T13:16:30Z</updated>
    <content type="text/plain">Please allow to select and copy OCR text from the document view.&#13;
&#13;
In the document view it's clearly visible, that the content has been recognized by OCR. When hovering the mouse over any content it's highlighted. However, the current settings do not allow selecting and copying it into the clipboard. Currently, if you need a useful information from the document, you must read and write it manually, which is laborious and prone to error. This restriction is unfounded.</content>
  </entry>
  <entry>
    <title>Logic for Line Item Validation</title>
    <link href="https://feedback.parashift.io/suggestions/591043/logic-for-line-item-validation"/>
    <id>sug_pxkpemb1pszixdl</id>
    <published>2024-10-31T09:17:58Z</published>
    <updated>2025-11-12T05:50:54Z</updated>
    <content type="text/plain">It should be possible to have checks over the extracted Data. For example if there are 4 line items with amounts, the sum of these items should match to the extracted total amount.</content>
  </entry>
  <entry>
    <title>Increase of limits for document size</title>
    <link href="https://feedback.parashift.io/suggestions/585589/increase-of-limits-for-document-size"/>
    <id>sug_nnwb8oqnrbbvvmq</id>
    <published>2024-10-03T13:24:39Z</published>
    <updated>2025-11-12T05:51:04Z</updated>
    <content type="text/plain">As mentioned in the ticket with the reference number 3851103598, the processing of large documents in Parashift fails. As a result, the documents cannot be further processed in a downstream process. I therefore request an increase in the maximum document size from 20 MB to 200 MB.</content>
  </entry>
  <entry>
    <title>Merge documents of a batch</title>
    <link href="https://feedback.parashift.io/suggestions/583183/merge-documents-of-a-batch"/>
    <id>sug_1nnx71utfrp3shj</id>
    <published>2024-09-23T06:24:02Z</published>
    <updated>2024-11-01T13:16:30Z</updated>
    <content type="text/plain">This applies in particular to uploads via e-mail. &#13;
Currently, all attached documents of a mail are merged and treated as one document in the classification and extraction steps (unless a separation has been configured). However, the output files provided are then only available individually. &#13;
It would be good to be able to configure this so that all documents are merged into one PDF, even for downloading. &#13;
Use case: Invoices and work reports are submitted separately by the supplier, but should be available as one document in the subsequent approval workflow and for archiving.</content>
  </entry>
  <entry>
    <title>Convert documents to PDF</title>
    <link href="https://feedback.parashift.io/suggestions/583182/convert-documents-to-pdf"/>
    <id>sug_0rwqxtk22gle2k4</id>
    <published>2024-09-23T06:15:00Z</published>
    <updated>2024-11-01T13:17:02Z</updated>
    <content type="text/plain">Uploaded documents that cannot be processed due to their mime type should be automatically converted to PDF.&#13;
This is of course pointless for audio or video files, but there are various quasi PDF variants that cannot be processed so far.</content>
  </entry>
  <entry>
    <title>Last login date information per user</title>
    <link href="https://feedback.parashift.io/suggestions/581348/last-login-date-information-per-user"/>
    <id>sug_9yxskspsorxf1e4</id>
    <published>2024-09-13T07:03:51Z</published>
    <updated>2025-11-12T05:51:21Z</updated>
    <content type="text/plain">This information is required to detect inactive users in order to have up-to-date access management, which is important for security reasons. Users with the “user admins” right should have access to this information.</content>
  </entry>
  <entry>
    <title>Validation: Create teams, assign document-types to teams</title>
    <link href="https://feedback.parashift.io/suggestions/579004/validation-create-teams-assign-documenttypes-to-teams"/>
    <id>sug_vttmea8onwxn8hx</id>
    <published>2024-09-02T15:23:52Z</published>
    <updated>2024-11-01T13:17:02Z</updated>
    <content type="text/plain">Add the ability to assign users to teams.&#13;
Add the option to assign document-types to teams.&#13;
Members of a specific team shall only be able to see documents assigned to their team.&#13;
Usage of validation levels shall be possible.</content>
  </entry>
  <entry>
    <title>Configuration Logs</title>
    <link href="https://feedback.parashift.io/suggestions/574304/configuration-logs"/>
    <id>sug_8wawrmukhl909rx</id>
    <published>2024-08-13T15:48:34Z</published>
    <updated>2024-11-01T13:17:02Z</updated>
    <content type="text/plain">Add logs of changes to fields, fieldsets and document types to the UI.</content>
  </entry>
  <entry>
    <title>Restrict classification on first page</title>
    <link href="https://feedback.parashift.io/suggestions/566132/restrict-classification-on-first-page"/>
    <id>sug_rjucjtqzixdayzg</id>
    <published>2024-07-10T12:04:38Z</published>
    <updated>2024-11-01T13:17:02Z</updated>
    <content type="text/plain">For some clients, it would help to restrict the classification on the first page of a document because the following pages are attachments.</content>
  </entry>
  <entry>
    <title>Chat with PDF capability via API</title>
    <link href="https://feedback.parashift.io/suggestions/560931/chat-with-pdf-capability-via-api"/>
    <id>sug_nd7tkoxbslvzddl</id>
    <published>2024-06-14T16:28:28Z</published>
    <updated>2025-11-12T05:59:46Z</updated>
    <content type="text/plain">One of the customers would like to use the chat function outside the Parashift system boundary.</content>
  </entry>
  <entry>
    <title>Restrict access to "own" documents</title>
    <link href="https://feedback.parashift.io/suggestions/557003/restrict-access-to-own-documents"/>
    <id>sug_urnwjleh6rw0pal</id>
    <published>2024-05-27T12:07:40Z</published>
    <updated>2024-11-01T13:17:19Z</updated>
    <content type="text/plain">We'd like to use the extraction screen for the end-users auf our application but we are not allowed due to data access issues.&#13;
&#13;
Use case: A user sends a document from our application to Parashift via API.&#13;
If recognition is not good enough this user should be able to do the validation in Parashift.&#13;
The problem is, that the user would also see all other documents from the other users.&#13;
But this user should only be allowed to see the documents that he sent via API. His "own" documents.&#13;
Therefore it must be possible to set the access-user(s) via API on a document.&#13;
A new role like "Validation of own documents" would be needed in Parashift.</content>
  </entry>
  <entry>
    <title>Provide synchronous interface for LLM worker</title>
    <link href="https://feedback.parashift.io/suggestions/550130/provide-synchronous-interface-for-llm-worker"/>
    <id>sug_maltzh7khhidfkd</id>
    <published>2024-05-02T10:10:07Z</published>
    <updated>2025-11-12T05:56:47Z</updated>
    <content type="text/plain">Enable chat with document outside of Parashift's GUI.</content>
  </entry>
  <entry>
    <title>Management of role-based authorizations via single sign-on (SSO)</title>
    <link href="https://feedback.parashift.io/suggestions/547843/management-of-rolebased-authorizations-via-single-signon-sso"/>
    <id>sug_rfmoghnlfrzweql</id>
    <published>2024-04-24T08:20:09Z</published>
    <updated>2025-11-12T05:51:54Z</updated>
    <content type="text/plain">SSO Login&#13;
Ability to log in via Entra ID user account.&#13;
&#13;
Automatic Detection&#13;
Post-login automatic identification and data retrieval via GraphAPI from Entra ID/OAuth endpoint.&#13;
&#13;
Role-based Access Control&#13;
Apply user roles assigned in Entra ID; assign different permissions in the - application based on roles.&#13;
&#13;
Role Management&#13;
Central role assignment through Entra ID; changes to reflect after re-login.&#13;
&#13;
Security and Compliance&#13;
Adherence to current security standards for secure authentication.&#13;
&#13;
Technology&#13;
Use of OpenID Connect via OAuth 2.0 Flow.&#13;
&#13;
Validation&#13;
Ability to validate Identity Tokens (JWT).&#13;
&#13;
Token Claims&#13;
Extraction of user roles from token claims.</content>
  </entry>
  <entry>
    <title>Apply Transformers in Manual Validation</title>
    <link href="https://feedback.parashift.io/suggestions/547203/apply-transformers-in-manual-validation"/>
    <id>sug_6hodwxkds9nzozg</id>
    <published>2024-04-22T08:00:52Z</published>
    <updated>2024-11-01T13:17:54Z</updated>
    <content type="text/plain">If you manually capture a value for a field with transformers, contrary to the automatic extraction, you have to manually add the transformation.&#13;
We need automatic transformation on manual validation, similar to the currently existing data output type: date transformation.</content>
  </entry>
  <entry>
    <title>Automatically redact documents</title>
    <link href="https://feedback.parashift.io/suggestions/546343/automatically-redact-documents"/>
    <id>sug_o7e8cslrzrqtse7</id>
    <published>2024-04-17T09:23:36Z</published>
    <updated>2025-11-12T06:01:03Z</updated>
    <content type="text/plain">A large insurance customer wants Parashift to automatically identify and redact sensitive data such as direct or indirect identifying documents.</content>
  </entry>
  <entry>
    <title>Automatic document deletion after x days/weeks</title>
    <link href="https://feedback.parashift.io/suggestions/544640/automatic-document-deletion-after-x-daysweeks"/>
    <id>sug_dzeshexqcmwkdza</id>
    <published>2024-04-09T06:29:38Z</published>
    <updated>2024-11-01T13:33:50Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>Classify confidentiality levels</title>
    <link href="https://feedback.parashift.io/suggestions/543346/classify-confidentiality-levels"/>
    <id>sug_xnh9y8d2h82ig2u</id>
    <published>2024-04-04T09:05:49Z</published>
    <updated>2025-02-10T12:57:30Z</updated>
    <content type="text/plain">Certain customers have documents that are classified according to different confidentiality levels. Some of them would like to be able to make this classification in Parashift.</content>
  </entry>
  <entry>
    <title>Get active document types from API call</title>
    <link href="https://feedback.parashift.io/suggestions/541712/get-active-document-types-from-api-call"/>
    <id>sug_ylethxowyubd0d8</id>
    <published>2024-03-26T09:40:02Z</published>
    <updated>2024-11-01T13:17:54Z</updated>
    <content type="text/plain">API call that returns a list of all active (production) document types with  fields for the tenant</content>
  </entry>
  <entry>
    <title>Better extraction validation support for processing of large plans</title>
    <link href="https://feedback.parashift.io/suggestions/539035/better-extraction-validation-support-for-processing-of-large-plans"/>
    <id>sug_shjgqn2syyn87mr</id>
    <published>2024-03-13T14:38:10Z</published>
    <updated>2024-11-01T13:18:15Z</updated>
    <content type="text/plain">1. Since the zoom level and resolution are not sufficent, in order to see details on large documents (e.g. large plans), it should also be possible to download PDF documents.</content>
  </entry>
  <entry>
    <title>Classification Validation: Choosing of doctype over keyboard</title>
    <link href="https://feedback.parashift.io/suggestions/539020/classification-validation-choosing-of-doctype-over-keyboard"/>
    <id>sug_xy3ec9gbxbuf4ud</id>
    <published>2024-03-13T14:22:19Z</published>
    <updated>2024-11-01T13:19:55Z</updated>
    <content type="text/plain">Classification Validation: In first level processing, for selection of a class a click on the class in the dropdown is needed. It is not possible to select it with the keyboard by e.g. pressing enter. Could be more efficient, if using only keyboard and if there would be configurable Shortcuts.</content>
  </entry>
</feed>
