Security & control
Built around the way campus IT works.
Understand how connections, credentials and access controls fit together. Bring your security team into the evaluation and validate the configuration against your institution’s requirements.
01 / Security & control
Local resources. An outbound connection.
The agent runs as a service on a Windows or Linux server. It opens an encrypted outbound WebSocket connection to the relay and executes configured tasks for campus resources. It needs no inbound connections from the internet; its local setup interface listens only on the server itself.
- Your network must permit the required outbound connections.
- Agent-side profiles configure access to local directory, SIS and SQL Server resources.
- Allowed-command settings in the agent’s local interface limit what it will execute.
- Administrators can revoke agent access from the platform.
02 / Security & control
Keep every credential protected.
Stored secrets use authenticated encryption. On Windows, the agent uses a DPAPI-sealed key to protect its local credential storage.
- AES-256-GCM encryption is used for stored secrets and authenticated agent commands.
- Cloud and local connection types have different credential and permission requirements.
- Use service accounts with the permissions needed for the selected operations.
- Review connection ownership and credential rotation in your operating procedures.
03 / Security & control
Give staff the access their work requires.
Roles and permissions control administrative actions. Audit records and workflow history support operational review.
- Assign staff roles and granular permissions.
- Protect staff sign-in with an emailed six-digit code or OIDC single sign-on.
- Review audit log entries with the actor, action and timestamp.
- Use workflow run history to investigate individual step results.
- Include retention, exports and incident-response needs in your evaluation.
04 / Security & control
A security review for your campus.
Evaluate data fields, recovery contacts, connection scopes and retention needs against your institutional policies. Technical controls support your review; they do not replace it.
- Document which student fields your workflows use.
- Review your deployment and data-handling requirements with our team.
- Request a Data Processing Agreement and send your vendor questionnaire.
- Contact [email protected] for a security walkthrough.
Your next step
Let's map your first workflow.
Bring your systems, questions and requirements. We'll work through the handoffs together.