CapabilitiesPublished

Business assistant · Integrations and control

How ValueSpace works across business systems while consequential actions stay under your control

Q: What information should an approval item show?

It should expose the material scope of the action, such as recipient or target, subject, message body, changed values and attachments, so the authorised person can make an informed decision.

Q: Does one approval allow similar actions later?

No. Approval applies to the exact prepared operation. A newly generated or materially changed action needs its own matching decision.

Q: What happens if the external provider fails after approval?

ValueSpace reports the provider failure and does not claim that the action succeeded. The workflow can perform an appropriate bounded follow-up when one is safe.

Q: Are all listed integrations available to every business?

No. Availability depends on the tenant's configured connections, permissions and provider capabilities. Read, prepare and execute access may also differ within one integration.

One request can use the relevant connected capabilities, prepare a reviewable action and continue only within the exact authority that was approved.

About 8 minutesPublished: 24 August 2026 at 09:35Updated: 31 August 2026 at 12:23

Short answer

ValueSpace can coordinate work across the business systems and permissions configured for the current company, while presenting one assistant experience to the owner. Reading, searching and draft preparation remain separate from consequential actions: the exact message, file or change can pause for review, and only the approved operation proceeds with fresh authorisation and a real execution result.

Use one coordinated assistant across the capabilities available to the business

The available work depends on the current tenant's connected systems and permissions. ValueSpace selects the relevant domain capability for the request while keeping internal routing and provider credentials outside the owner's experience.

Connected mailboxes, calendars, commerce, websites, booking systems and communication channels can contribute where configured.
Two businesses can have different available actions without changing the one-assistant experience.
Each domain receives only the tools, instructions and approval boundary relevant to its work.
A listed integration is not automatically available to every tenant or user.

Separate reading, preparation and external action

Searching an inbox, preparing a reply and sending it are different capabilities. The same distinction applies to publishing, deleting, financial operations and selected changes to business records.

Read-only work can gather facts without changing the provider.
Preparation creates an exact reviewable draft or proposed change.
Execution requires the configured permission and approval where the action is protected.
Approval authorises one prepared operation, not broad future access.

Continue the same workflow after an authorised decision

The approval item shows the material details, stores the interrupted state and resumes the original work after approval or rejection. A changed action requires its own matching decision.

Request

Use authorised context

Prepare

Exact action and files

Decide

Approve or reject

Result

Execute and confirm

No action on rejection

Process diagram: From a connected request to an authorised and verified result The exact prepared action pauses for review, then either stops or continues with fresh authorisation and a real provider result.

Make recipients, values and attachments visible before approval

A protected action should not hide its consequences behind a generic confirmation. Reviewable details can include the recipient, subject, body, attachments or affected record, and every referenced file must already belong to the authorised scope.

ValueSpace

Business work, clearly controlled

Connected action

Business owner
Send the approved proposal to our project contact.
ValueSpace
I prepared an email to the contact stored in the authorised project. Subject: Updated proposal. The message refers to the agreed scope and attaches the approved PDF.
Attachment
approved-proposal.pdf
Existing project file selected for this exact action.
Waiting for approvalOne recipient, one attachment
Business owner
Approved for this recipient and this attachment.
Authorisation recheckedExecuting the prepared action
ValueSpace
The configured mail provider accepted the message. The delivery record has been added to the project.
Connected action confirmed

Conversation scenario: A connected action exposes its full approval scope The example shows the recipient, wording and attachment before approval, then reports the provider result separately from the owner's decision.

Recheck authority and report the real provider result

The resumed action uses fresh tenant-scoped authorisation and resolves durable files again. Approval is not proof that an external provider accepted the operation, so the final response must distinguish authorisation from confirmed execution.

If approval state cannot be stored, the protected action does not run.
If an integration fails after approval, ValueSpace reports the failure instead of claiming success.
Provider credentials and raw attachment contents remain behind the integration boundary.
Read, prepare and act permissions can differ for the same integration.
Some channels require an established recipient conversation before delivery is possible.

How this works in ValueSpace

ValueSpace coordinates the configured capabilities while keeping consequential execution tied to an exact, reviewable and authorised action.

ValueSpace discovers only the business capabilities available to the current tenant and user.
Mail providers can appear through one connected-mailbox experience while credentials remain private.
Read-only work, draft preparation and external execution remain distinct capability levels.
A protected action is persisted and paused before the owner is told that approval is waiting.
Approval resumes only the matching prepared calls with fresh tenant-scoped authorisation.
ValueSpace receives the actual execution result and does not treat approval alone as successful delivery.

See a focused example for preparing and approving business messages and learn how approval can pause verified multi-step work.

Frequently asked questions

Does every connected action require approval?

No. The boundary depends on the operation, provider and configured policy. Reading and preparation can remain non-consequential, while sends, publishing, deletion, financial actions and selected mutations can require approval.

What information should an approval item show?

Does one approval allow similar actions later?

What happens if the external provider fails after approval?

Are all listed integrations available to every business?

Prepare connected actions for informed approval

Consequential actions are safer when the authorised person can see the exact target, values and attachments before execution.

Connect only the business systems required for the workflow.
Keep read, prepare and execute permissions aligned with each role.
Review recipients, changed values and attachments before approval.
Treat the provider result, not the approval click, as confirmation of execution.

Related resources

CapabilitiesWhat an AI business assistant can do for a small business CapabilitiesHow an AI business assistant works with documents and files

Back to all resources