An illustrative example: a specification link is sent from one system to another. It opens for the administrator but asks the person doing the work to sign in. The record says “transferred”, yet the recipient cannot use the attachment. The integration delivered an address, not necessarily access.
If a company uses different applications for sales and delivery, choose in advance whether to send a link to the source document or a separate copy. The options need different rules.
A link and a copy serve different needs
A link leads to a document in the original system. Recipients need suitable permissions and a way to open it. A copy lives on the other side, so changes to the original do not appear automatically.
Specify what the employee needs: the current working version or a file fixed at an agreed point in time. The name “specification” does not explain which outcome is correct.
Clarify the address the integration transfers
In Bitrix24, a link opening a file in the interface differs from a download address. The official file download guide also explains that retrieval depends on storage and file attachment relationships. Downloading requires permissions and the relevant method's access scope.
Do not turn a technical address containing access parameters into a shared employee link. Ask the developer to explain who retrieves the file and whose rights the exchange uses. Check REST API availability, the software exchange interface, and the second system's restrictions separately.
Test an ordinary recipient
Test with a real participant's permissions rather than administrator rights. Open the attachment from the required record, then repeat after signing out of the original system. This reveals dependence on an unnoticed active session.
For an external recipient, decide separately whether public access is appropriate. Bitrix24 link settings and restrictions are covered in the file access guide. Do not enable public access merely to conceal an exchange error.
For a team in Kazakhstan, check working languages in names, Cyrillic filenames and access from the devices used.
Agree on updates and failures
Replace the source document with a test new version. Check that the recipient sees the agreed behaviour: the current linked file or the previously fixed copy. Updating a copy, if required, is a separate integration action.
Test denied access, a deleted file and a repeated transfer. A download failure should be visible to an owner; “delivered” must not mean merely saving a string containing an address.
QQDev develops integrations through the Bitrix24 REST API. On the service page, discuss attachment transfer while retaining the company's current system if its interface supports the required scenario. Bring an anonymised file and explain who needs it, where it should open and which version is correct.