Delegate work. Define access.
Your clients' data, your company's data and Nementium's resources need clear boundaries. We combine team permissions, agent identities and reviews to define who can view information, edit records and use tools in configured workflows.
Control starts with each resource
People. Permissions distinguish between viewing, acting and editing on objects that support them. Sharing a project, task or workspace has a defined scope.
Agents. Database identities can limit access by table and operation. Assigned connections determine which configuration each agent receives for its work.
Tools. Messaging tools associate the work with a specific agent and resource. Preparing a draft and sending it are separate actions.
Email. Sending from the email tool requires an authorised person and explicit confirmation when that channel is enabled. The workflow retains the message and its versions.
What an agent harness is and why it matters
A harness is the environment that organises an agent's execution: it connects the agent's identity, instructions, available tools and control mechanisms. Its design shapes what the agent can do and how its work is reviewed.
In Nementium, this approach connects data permissions, assigned connections and tools with a defined scope. Protection relies on technical controls at the relevant layers; each workflow's scope is established during configuration.
People and agents
Team permissions.
Agent identity.
Access and reviews
View, act or edit.
Review before execution.
Process resources
Data and connections.
Tools and email.
Viewing, preparing and sending are separate decisions
Consider an initial sales contact. The agent prepares a draft using the lead's context. A person reviews the recipient and message. Sending from the email tool is confirmed separately, when enabled and when that person has permission.
This journey separates delegated work from authorised action. Record history and message versions help you review what happened within the workflow.
Lead context
Available information
Agent draft
Prepared message
Team review
Recipient and content
Confirmed send
Authorised person
A shared principle for client data and our own resources
When configuring a process, we review the data it needs, the people involved, the agents and the connections they will use. The aim is to grant access according to each participant's work.
That principle applies both to client work and to Nementium's own operations. Every connection and new task must be reviewed within its scope.
Visibility to review and refine
Team permissions, record assignment and history help maintain accountability for the work. You can consult changes and versions in the records and tools that include this tracking.
During setup, we agree on which actions need review, what data the workflow uses and who should step in when information or access is missing.
Questions about control and security
Is an agent harness the same as a user permission?
A user permission determines what a person can view or do. The harness organises agent execution and connects its tools and control mechanisms. They are related layers with different responsibilities.
Do all agents have the same access?
Nementium lets you assign database identities and connections according to each agent's work. The effective scope is defined and checked in each configuration.
Does preparing an email allow it to be sent automatically?
In the email tool, preparing and sending are separate actions. When sending is enabled, an authorised person reviews and confirms the action. Other channels are defined according to their tools and connections.
Can we review access before starting?
Yes. The process scope should specify what information it needs, which tools it uses and what responsibilities the team will have. That review is part of defining the work.
Define what to delegate and who can act.
Let's review your process, the data it needs and the controls that should accompany it.