Separate account responsibilities
Agent accounts establish target connections. Task accounts determine the identity used to execute the script. Accounts may be authorized for one role or both.
CUVENA / SECURITY
Control belongs in the workflow.
Clear account roles, scoped access and visibility at every execution stage.
Choose where credentials live
Centrally managed credentials are stored encrypted in Cuvena and delivered to the assigned agent with the job. Agent managed passwords stay in the local protected vault; account metadata synchronizes.
Limit access by scope
Organization and space assignments define access to resources. Sharing a script does not automatically share target servers or credentials.
Make controlled changes visible
Use live script versions, approval requirements and audit records to manage operational responsibility.
Troubleshoot without exposing passwords
Diagnostic reports show execution stages, error codes and relevant context. Passwords, tokens and credential payloads are excluded from support exports.
Respect the target’s security model
Server permissions, authentication methods and operating-system policies remain in force. A Cuvena account assignment does not override Windows or Linux access controls.
A FEW IMPORTANT DETAILS
Questions,
answered.
Can agents update without a desktop prompt?
After a one-time v44 administrator or root installation, signed updates can be requested for selected agents. Platform admins control customer offers; customer owners and administrators can update their own agents. The updater waits for work to finish, verifies the new heartbeat and attempts rollback on failure. Operating-system policies still apply.
Where do scripts execute?
On the selected target servers through your execution agents. Cuvena provides central management, dispatch and visibility.
Do I need the same account for the agent and the task?
No. You can use the agent connection account or assign a separate task account, provided the account is authorized and the target permits the requested execution.
Can I use credentials stored on the agent?
Yes. Agent managed account details appear in the platform, while the password remains in the protected local vault. Centrally managed accounts are managed in Cuvena.
Will a script open a window on my desktop?
Background execution does not display application windows in the signed-in user’s desktop session. Verify returned output or the intended file or system change.
What happens if the connection is lost?
An execution can require outcome verification when completion cannot be confirmed. Review the result before retrying uncertain work to avoid running a script twice.
SUPPORT WITH ACCOUNTABILITY
Troubleshoot together.
Keep responsibility clear.
Cuvena support workspaces let authorised platform staff investigate an organisation without asking for a customer's password or replacing their login.
Standard access requires customer approval by default and starts read-only. Platform owners and separately authorised privileged support staff can investigate without an individual customer approval. Platform owners are not required to use an authenticator for support access. Both modes identify the staff member and record activity in the organisation and platform audit logs.
Read how support access worksACCOUNT ACCESS
Precise permissions. Practical recovery.
Platform owners can assign detailed Admin roles to administrators and support staff. Optional authenticator setup includes a scannable QR code and single-use recovery codes. Enabled authenticator protection is enforced at sign-in.
Read the access and recovery guideCUVENA SCRIPT MANAGER