Just wanted to confirm that, this is not possible in IFS Cloud core. (Probably you already knew it). It was a purposely taken design in order to avoid risks of exposing preliminary/In Progress documents, to B2B stake holders. What is the use case here, if you may explain?

It has to be a definite but a small mod, if you need to achieve this.

Access to preliminary documents allows B2B suppliers to verify and validate essential information and enables better collaboration and communication between service providers and asset manager. It allows both parties to share, and review documents, fostering effective collaboration on projects or resolving issues more efficiently.

Thanks. Could it be workaround by Document Revision handling?

We 

We offered that workaround as well. Thanks for quick response.

I don't see a conflict with that and working with released documents. Released does not necessarily mean things are final, you can decide on other ways to signal that. A common way is to use the Document Revision field for that. For example, during collaboration, you can work with numeric values (1, 2, 3, ...) and once things are settled you work with letters. Or the other way around, or combining both The important thing is that all parties know how things work.

Part of the requirement that we have for a similar process, is that when the Document is uploaded on the b2b portal, the end client would like to approve the documentation - prior to it being released.

If the contractor is uploading important compliance documentation relating to the equipment they have serviced - and make a mistake - the IFS customer would like to then reject the document.  We can get around this by using supplementary revisions - but seems inefficient. 

The document access rules are robust enough to control access on a document by document basis - it should not matter on the document status itself on who should get access. 

@Mayura Wasantha IFS should be designed in a configurable way. We’ve hard-coded this logic, that fails half time in real life. @jami  example is very valid. I have another that many document revisions are not even approved in IFS because worked outside and just uploaded in IFS to be used alongside transactions. Us, as presales, even developped a BPA to automatically release a document when it is posted in B2B. What’s the next step going forward ?

In our example, the supplier uploads a certificate of works completed using the B2B portal.  There may be several reasons why the company would reject this certificate and expect the supplier to upload a replacement. 

The document classes that are exposed to the B2B and the Access security per document class should be enough to secure the document to that individual person and internal people.

We have the Ideas section in IFS Community for the purpose of asking for new features to be considered.