Since I’m currently self-hosting and I’m not familiar with n8n cloud, I have two questions as I’ll need to know how it works for my work:
For how long are the execution logs kept? (Privacy issue)
How exactly do the roles work? e.g. can I log in as an editor while my customer is the administrator and make some manual changes?
Thanks in advance, and I would really appreciate any additional feedback by someone with hands-on experience at shipping workflows.
Execution log retention in n8n Cloud is tied to your subscription plan. Logs are pruned automatically based on either a time limit or a maximum number of saved executions, whichever comes first.
Yes. If your customer is the Project Admin (or Instance Admin) and you are assigned the Project Editor role for that project, you have full permission to:
Hi @kalouseskimon-dot
For the privacy concern, the control that matters is what gets stored, set per workflow. Open Workflow Settings (three dots, top right) and set Save successful production executions and Save failed production executions to Do not save, and turn off Save manual executions, so sensitive execution data is never written to begin with, independent of the plan retention.
If you need to keep the execution record for monitoring but hide the input/output payload, that is the Redact production execution data setting, available on Enterprise Cloud:
On the roles question, the editor/admin split you described depends on the Project Editor role, which on Cloud requires the Pro plan or above (the entry Starter plan doesn’t include it). So your customer’s account needs to be on Pro or higher for you to sit as Project Editor while they hold Project Admin.
Thanks a lot! Your response was crystal clear!
Really helpful response, thank you!
Just one more question: is it a good choice in the starter plan to give my customer a json containing the workflow, and all they have to do is to import it and fill in their credentials?
From what I know:
Execution logs: The retention period depends on the n8n Cloud plan. Different plans keep execution history for different lengths of time, so it’s worth checking the plan details if privacy or compliance is important.
Roles: Yes, n8n Cloud supports role-based access. Typically, a workspace owner or admin can invite team members with roles such as Editor. An Editor can build and modify workflows but doesn’t have the same administrative permissions as the workspace owner (for example, billing and some workspace settings).
I’d also be interested in hearing from someone who actively uses n8n Cloud in production—especially agencies managing customer workspaces. How do you usually handle customer access versus your own maintenance access?
I told you you’d get a good answer here 
Hi @kalouseskimon-dot
That works, and it’s a clean handover on Starter. A workflow export carries the node structure and credential references (names and IDs) but not the secret values, so your customer imports the JSON and creates their own credentials, and none of your secrets travel with the file. They import from the three dots, top right, Import from File.
Before handing it over, open the JSON and anonymise the credential names, and check any HTTP Request node built from a cURL import, since those can carry auth headers inside the file.
