Riftur Now Supports Organizations, Review Sharing, and OCR
By Jude Canady
Cover More of the Review Workflow
Riftur now supports organizations, controlled review sharing, and OCR across scans, standalone images, and images embedded in Microsoft Office files. These are substantial changes to the operating reach of the platform. A review can begin with a broader range of source material, remain connected to a team and its proposal history, and reach internal or external stakeholders without leaving Riftur. The analysis remains central, but the workflow surrounding it is now considerably more complete. Teams can manage more of the review process without reconstructing its context in other systems. Every review is shaped by two practical boundaries: what Riftur can read and who can act on the results. OCR expands the first boundary by making previously inaccessible content available for analysis. Organizations and sharing expand the second by giving teams clearer control over membership, ownership, privacy, and distribution. Submission Groups preserve the relationship between authors, reviews, and proposal versions as that work moves forward. The result is a stronger system around the review, not simply a larger collection of features. Each addition supports the same objective of helping teams turn proposal evidence into visible, controlled action.
Organizations Bring Work Into One Place
Proposal reviews often begin with one person even when the proposal belongs to a much larger team. A proposal manager may initiate the analysis, but technical leads, capture managers, writers, executives, and quality reviewers may all need the results. When the review exists only within an individual account, the team must recreate its working structure elsewhere. Findings move into emails and meetings while access depends on whoever created the original analysis. Later contributors may not know which review represents the current proposal. Responsibility can move while the review remains attached to an earlier stage of the pursuit. This makes continuity harder than it needs to be. Riftur organizations provide a shared environment for managing that activity. An organization can include multiple members while preserving the identity of the person who created each review. The Reviews page displays authorship alongside the relevant Submission Group and proposal version. Members see “You” on their own work and colleague email addresses where attribution matters. The shared workspace becomes a visible record of proposal activity rather than an anonymous collection of documents. This structure remains useful as responsibilities change. A proposal may begin with one manager and later pass to another. A technical lead may need an earlier review before responding to a new finding. An executive may need visibility without assuming ownership of every analysis. Keeping the work within an organization reduces the need to rebuild access during each transition. The proposal history stays connected to the company while individual responsibilities continue to evolve. The system preserves continuity without hiding who performed the work.
Roles and Invitations Support Real Teams
Not every organization member needs the same authority. Riftur supports Owner, Admin, and Standard roles so companies can separate workspace administration from ordinary review activity. Owners retain responsibility for the organization and its billing relationship. Admins can assist with membership and organization management. Standard members can participate in review workflows without receiving every administrative control. Ownership transfers and member changes remain deliberate actions handled by people with the appropriate authority. Members receive clear guidance when an action requires help from an Owner or Admin. The role model creates practical boundaries without turning permission management into another proposal process. Teams can understand who controls the workspace and return their attention to the work inside it. Organizations can invite contributors individually or prepare several invitations at once. An administrator can stage multiple recipients, assign the appropriate role to each person, and send the invitations together. Active members and pending invitations are reflected in the organization’s per seat subscription quantity. This keeps reserved access aligned with billing while recipients complete the acceptance process. The interface shows when invitations are being sent, reducing uncertainty during actions involving both billing and email delivery. Administrators can see who has joined and who still has an invitation pending. Invitation acceptance also continues through the authentication path required by each recipient. An existing user may sign in before joining. A new user may need to register and confirm an account. Another recipient may use an email link or Google authentication. Riftur retains the invitation destination through those steps and resumes acceptance afterward. Account setup does not need to interrupt the reason the person was invited.
Ownership and Privacy Remain Visible
A shared organization should not automatically expose every piece of work a member created before joining it. Someone may have used Riftur independently before becoming part of a company workspace. Their earlier Submission Groups may involve unrelated pursuits or customer material that was never intended for the new organization. Automatically sharing that history would simplify access while weakening an important privacy boundary. Riftur keeps preexisting personal groups private unless their author chooses to share them. Members can join an organization without surrendering control of previous work. New organization Submission Groups also begin with deliberate visibility. The Reviews page provides a clear Private or Organization control for users permitted to manage sharing. Owners and Admins retain the access needed to oversee organization activity. Standard members can view and extend groups that have been shared with the organization. This allows one workspace to support both limited proposal activity and broader team collaboration. The team decides when a group should become part of the organization’s shared workflow. Access does not expand merely because another account exists in the same organization. Authorship remains visible after a group is shared. A member can see who created the review and who owns the surrounding proposal context. That information becomes useful when a finding depends on a decision that occurred outside the uploaded documents. The reviewer knows whom to contact instead of treating the result as an orphaned system record. Privacy controls manage visibility, while attribution preserves accountability.
Submission Groups Preserve Proposal History
One proposal may pass through several drafts before submission. A new review should reflect the current document without erasing the context established by earlier versions. Riftur Submission Groups connect those reviews under a recognizable proposal name. Each version retains its documents, author, creation time, processing status, and score. The team can follow proposal development without treating every analysis as an unrelated event. The relationship between versions remains visible even as the underlying files change. That continuity gives the review history a stable place inside the organization. A Standard member can open a shared group and add a later version when permitted. Owners and Admins can understand which proposals are active and who is contributing to them. Authors remain visible, so version history does not become anonymous after collaboration begins. The group records how the proposal developed while the access model determines who can participate. Team members can return to the same proposal context whenever another draft is ready. Review history becomes part of the workflow rather than a collection of isolated results. The system also avoids preserving empty Submission Groups when an initial analysis does not complete successfully. This keeps failed attempts and unused names from cluttering the organization’s working record.
Reviews Can Reach People Outside the Organization
Organization membership covers the people who work together regularly, but completed reviews often need to reach a broader audience. A subject matter expert may need to inspect findings for one section. An executive may need the results without joining the organization. A partner may require temporary access to a specific review. Riftur supports both private recipient sharing and anonymous public links for these situations. The review can move beyond the immediate workspace without first being reduced to an email summary or static export. Private sharing connects access to a named recipient. Riftur sends a branded email that identifies the review and guides the recipient toward the appropriate access path. If the person does not yet have an account, the process can take them through registration before opening the shared material. Existing users can authenticate and continue directly to the review. The destination remains available while the recipient completes those steps. Access stays connected to the intended person rather than circulating as an unrestricted file. The owner gains a clearer understanding of who can open the review. The recipient receives the findings with their score context and supporting details intact. Private access can be revoked when it is no longer appropriate. The owner can remove a recipient without deleting the review or changing internal organization access. Failed email delivery can also be retried from the sharing workflow. Private sharing therefore remains a manageable access decision rather than a permanent transfer of the review. The owner retains control as contributors and responsibilities change.
Public Links Serve a Different Audience
Some reviews need wider distribution than named recipient sharing provides. A proposal manager may need to brief a temporary review group whose membership is still changing. A consultant may want to distribute findings without creating an account relationship for every stakeholder. In those cases, Riftur can create an anonymous public link for a completed review. Anyone with the active link can open the shared view. The review remains private until the owner deliberately enables public access. If circumstances change, the owner can disable the link without deleting the underlying review. This provides more control than distributing a report that cannot be recalled after delivery. Public links and private recipients give teams distinct ways to match review access to the audience.
OCR Expands the Source Material
Proposal evidence does not always arrive as clean digital text. Teams work with signed forms, scanned solicitation pages, screenshots, customer letters, diagrams, and older performance records. A person may be able to read the information while the file contains nothing that normal text extraction can access. The upload appears complete, but some of its content remains absent from the analysis. That creates a blind spot between what the reviewer sees and what the system can evaluate. OCR reduces that gap by recovering visible text from image based material. More of the original source can participate in the review without manual transcription. Riftur now applies OCR to supported standalone image files. The platform can extract visible text from BMP, GIF, JPEG, PNG, TIFF, and WebP files. A photographed page or exported diagram can enter the same analysis workflow as a conventional document. This is useful when an image contains a qualification, result, date, label, or other detail relevant to the proposal. The source does not need to be rebuilt in Word simply to become readable by the system. Teams can upload the material in the format they actually received. Fully scanned PDFs receive similar treatment. Riftur first checks whether the PDF contains native text. When every page lacks readable native text, the platform renders the document and processes the pages with OCR in their original order. Page markers remain part of the extracted content so the analysis retains basic source structure. An image only solicitation or supporting attachment can therefore contribute to the review instead of appearing as an empty source. The team can preserve the original file while making its visible text available for comparison. OCR extends document support at the point where ordinary extraction would otherwise stop.
Important Evidence Often Lives Inside Office Files
Images are not limited to image files. Proposal teams routinely place diagrams, screenshots, scanned letters, organizational charts, and process graphics inside Microsoft Office documents. The surrounding Word paragraphs or PowerPoint text boxes may extract correctly while the image carries the most important statement. A reviewer can see that image, but ordinary document extraction may not capture its wording. Relevant evidence can disappear from the analysis even though it remains plainly visible in the original file. Embedded content therefore needs attention alongside the document’s native text. Riftur now processes supported images inside modern Word, PowerPoint, and Excel files. Word documents contribute paragraphs and table content while OCR adds readable material from embedded images. Presentations contribute text from slide shapes and tables alongside text recovered from supported graphics. Workbooks provide visible cell values by sheet and add readable content found inside embedded images. This gives the review a more complete representation of what a person sees when opening the source file. The document does not have to choose between native extraction and image recognition. Both forms of content can contribute to the material Riftur examines. This improvement is particularly useful for proposal evidence. A past performance presentation may place measurable results inside a graphic rather than the slide body. A technical workbook may contain an inserted diagram whose labels explain the solution. A Word attachment may include a scanned customer letter or certification. OCR gives those elements an opportunity to inform the review without requiring the team to recreate the source. The analysis can draw from more of the information already present in the company’s files.
The Entire Review System Gains More Reach
These additions make Riftur better aligned with the way proposal work moves through a company. Source material arrives in many formats, and the people responsible for acting on it do not always share the same account structure. Some reviews belong within a long term organization workflow. Others need to reach an executive, partner, or temporary reviewer outside it. Proposal versions continue changing after the first analysis, while authorship and access decisions still need to remain clear. Organizations, sharing, Submission Groups, and OCR allow more of that activity to remain connected. The platform now supports a broader path from source document to completed review. Consider a scanned customer letter used to support a past performance claim. OCR can make the letter’s visible text available during analysis. The proposal manager can retain the review inside an organization Submission Group and share it with the technical lead responsible for the revision. A company executive can receive private access without becoming a permanent member of the workspace. If a broader review group later needs temporary visibility, the owner can enable a public link and disable it when the review ends. The evidence, analysis, author, proposal version, and access decision remain connected. Each capability supports a different part of the same working record.
A More Complete Riftur Experience
The practical impact extends beyond any individual feature. Teams can bring more representative source material into the analysis. They can preserve proposal history across versions and contributors. They can distribute findings according to the needs of each audience. Access remains deliberate even as participation expands. Review activity becomes easier to follow because authorship and proposal context remain visible. Proposal teams should not have to recreate readable source material simply because it arrived as a scan. They should not need to transfer review findings into disconnected systems whenever another person needs access. Riftur now reduces both forms of friction. More of the document becomes visible, and more of the team can participate without losing control of the review. The proposal remains connected to its authors, versions, and supporting evidence. These additions make Riftur a more complete system for moving from proposal content to informed action.
If you have questions, feedback, or want to learn more about how Riftur is used, contact us. You can also visit our home page at riftur.com to start testing the platform for your use case. Read other posts on our blog for related topics and updates on Riftur.
© 2025 Riftur — All Rights Reserved