Find answers. Get support. Join conversations.

We're building an integration between a third-party document signing service and SuperOffice using n8n. When a document is signed, a webhook triggers our flow which: Updates the Sale status to Sold Creates a Document entity (POST /api/v1/Document) Downloads the signed PDF Uploads PDF content (POST /api/v1/Agents/Document/SetDocumentStreamFromId) Everything works - the document is created, PDF is uploaded, I can open it. But other users cannot open the PDF, even though: VisibleFor is set to "All" Associate is set to the Sale owner Both users have full admin permissions (User level 0, all data rights set to Delete) We use the default SuperOffice document library (not SharePoint) API calls are authenticated with my OAuth credentials (Authorization Code flow). The document shows CreatedBy = me, even though Associate = other user. We verified the PDF is actually stored - GET /api/v1/Document/{id}/content returns the full PDF data. Is this a known limitation? Do we need a system user or separate integration account for document uploads to be accessible by everyone?

Hi again Any chance there's another functional right that doesn't give you admin access that works as a workaround while we wait for the fix, seeing as List tables doesn't seem to help? Espen

Hi Adam, Yes, I see that it is different depending of the provider. That is why it works sometimes. We will update this so that for UK companies, the numbers will come first always. Best regards Filip Norman Product Manager

Hi Samuel, We have stopped Tickets-Loops on Time as it happened on Nov. 28th and merged all 275 looped Tickets in one Ticket. This Issues was by our cust20815 only on Nov. 28th i guess caused by our Email-Filter that didn't work. before this date everything ran well. And after Issues on Dec. 1th I have tested with our Partner Ticketsystem Skaylink Support who's Auto-Reply caused this Tickets-Loops, we sent Emails and Replies to the Ticketsystem each other, and there was no new Tickets-Loops.  On 28th Nov. I got also 33 Email Notification from noreply@statuspage.io about Issues in Mailgun. My Question is, was that Issues in Mailgun sth. to do with the Tickets-Loops on Nov. 28th, that our Email-Filter didn't work, and how to avoid this in the Feature? Since Once the Loops happened, the Ticketsystem runs so well as it was  paralyzing and all our User cannot live work on Ticketsystem to check and send Feedbacks to our Customers. the Email-Filter should keep working.   Thanks a lot!

Ah, thanks! I was searching for a bug report by searching the displayed message but wasn't able to find it.

Exciting update for pilot users: New version 4 released this week! We are delighted to announce the release v4 of Custom Objects available this week for our pilot users. As we continue to enhance your experience, this update introduces new features and improvements. Here’s what’s new in v4 (Release 11.5): Enable a Custom object as a Full Entity in Navigator. Included in Screen Designer, create your specific designs for all your Custom Objects. Access Rights to each Custom Object to control what your users can access. Read more in the  overview of Custom Objects Stay tuned for further updates as we continue to introduce more features in future releases. Enjoy the new capabilities in Custom Objects version 4!