Prepare a weekly project update from approved files.
Role: Project ManagerWorkflow: Client updates
1Sources checked
Project library + approved template
2Data check
One detail marked for review
review
3Route selected
Efficient AI · estimated usage visible
Efficient AI
4Manager review
Draft is ready for confirmation
Recorded: role · sources · route · review status
DEPLOYMENT AND DATA OWNERSHIP
Choose where the Workspace runs — and how much direct control your team needs.
Your workflow, approved sources, and AI rules can run in a Sunofla-managed Pilot, in your organization's cloud environment, or in a local / hybrid environment. The right choice depends on the work, the information involved, and the level of direct control your team needs.
A dedicated environment supports the agreed Pilot scope, with support and data-handling boundaries documented in the Pilot.
01
Sunofla-Managed Pilot
Start quickly with a dedicated Pilot environment.
A Sunofla-managed Pilot gives a small team a practical way to test one controlled workflow before making a larger deployment decision.
The Pilot scope, approved sources, user roles, and permitted AI routes are defined before real work begins.
BEST FOR
One workflow and a small Pilot group
Teams that want to validate the experience quickly
Early testing before a longer-term decision
Sunofla operates the environment needed to deliver the approved Pilot scope. Support access and data-handling boundaries are documented with the Pilot.
Files, workspace data, backups, and AI credentials can remain in the environment controlled by your organization. Support access is approved, limited, and recorded.
02
Customer-Owned Cloud Workspace
Deploy in your cloud account. Use your AI account.
The Workspace is configured in cloud infrastructure controlled by your organization. Files, databases, vector indexes, and backups can remain in that environment, based on the deployment design.
Sunofla provides the Workspace template, workflow setup, access rules, routing policy, testing, and implementation support.
BEST FOR
Teams with sensitive project or client information
Organizations that want direct ownership of their cloud environment
Teams already using approved cloud or AI accounts
YOUR TEAM CONTROLS
File storage and approved knowledge sources
Database, vector index, backup, and retention settings
AI provider account and API credentials
User roles, cloud-routing rules, and support access
Selected services can run locally, while approved work may use a customer-controlled cloud AI account when the workflow allows it.
03
Local / Hybrid Workspace
Keep selected work close to the team. Use cloud AI where it adds value.
A Local or Hybrid Workspace runs selected services in your office or local environment. Files, shared storage, and local AI capability can remain close to the team, while approved tasks may use your organization's cloud AI account when the workflow allows it.
BEST FOR
Large files or active shared project data
Teams that need local storage, backup, or recovery capability
Workflows that need both local control and selected cloud capability
A Pilot can begin in a dedicated cloud workspace. Local capability can be added when it supports the workflow.
DATA HANDLING, IN PLAIN LANGUAGE
See what is connected, where it runs, and who can access it.
For a customer-owned cloud or Local / Hybrid deployment, customer files, workspace data, vector indexes, backups, and AI credentials remain in the customer-controlled environment.
Sunofla can configure and support the Workspace without hosting the customer's source files or AI account. When support access is needed, it is approved, limited, and recorded.
A request follows visible rules.
The Workspace records the approved source, selected route, review requirement, and support activity around the work.
FOR CUSTOMER-OWNED DEPLOYMENTS
The Workspace, database, vector index, and file storage run in the customer environment.
AI provider credentials are created and controlled by the customer.
Customer files and full prompts are not copied to Sunofla-hosted storage or analytics systems.
Support access is approved by the customer, limited in time, and recorded.
Export, retention, backup, and deletion settings remain visible to the customer.
WHEN A WORKFLOW USES CLOUD AI
Cloud AI is used only when the workflow allows it.
The approved request or retrieval context is sent to the model provider selected by the customer, using the customer's organization account and policy. The Workspace records the selected route and the reason for it.
Cloud use is a workflow decision — not a hidden default.
A WORKSPACE OWNER CAN SEE
Approved sources
Who can use each workflow
Which tasks may use cloud AI
Usage, cost, review, and support-access records
The goal is to make the operating rules visible to the people responsible for the workspace.
The same Workspace controls access, data boundaries, AI routing, and review around each request.
HOW THE WORKSPACE GOVERNS ONE REQUEST
Four controls keep everyday AI work understandable.
The Workspace gives a team one practical path for using approved knowledge, choosing an appropriate AI route, and keeping people responsible for important decisions.
👤Signed-in userThe request starts with a known role.
→
🔒Role and source checkOnly approved files are available.
→
🛡️Sensitive-data checkHigher-risk details can be flagged or stopped.
→
🔀AI route selectedLocal, efficient, or premium — chosen by rules.
→
✓Review or approved outputSensitive actions stay with a person.
Each request follows the rules defined for that workflow.
ACCESS AND ROLES
People see the sources and actions appropriate to their role. Owners manage policies, managers review work, and staff use approved workflows.
○
OwnerManages policies and access
○
ManagerReviews work in the queue
○
StaffUses approved workflows
DATA BOUNDARIES
Rules can flag, mask, or stop higher-risk details before a request reaches an approved AI route. Unclear cases remain visible for review.
Project update draft
Client name: [masked]
Project amount: [review needed]
ROUTING AND COST VISIBILITY
Routine work can use efficient AI, while higher-cost routes are reserved for work that benefits from them. Route choice, usage, and review effort remain visible.
Local / privateFor selected internal work.
EfficientFor routine summaries and drafts.
PremiumFor higher-complexity work.
HUMAN REVIEW AND RECORDS
The Workspace can prepare drafts and summaries. A person remains responsible for sending, approving, changing records, or sharing sensitive information.
AI can helpSearch · summarize · draft
A person confirmsSend · approve · share
Activity record: Role checked · Sources used · Route selected · Review status
START WITH A REAL PILOT
Test one workflow with real work and clear boundaries.
A guided Pilot connects one approved workflow, a small group, defined sources, an AI route, and a review point. The team then reviews quality, exceptions, usage, cost, and review effort before choosing the next step.
Example Pilot — illustrative workflow
A 12-person design studio
Workflow
Search approved project files and prepare client update notes.
Allowed sources
Current project folder, approved templates, and team procedures.
Pilot availability is limited while we validate the product with a small number of Orange County teams.
REQUEST PILOT ACCESS
Start with one workflow your team already wants to improve.
Tell us where work slows down, where access is unclear, or where AI use feels hard to control. We’ll help identify a practical Pilot boundary and the right environment for the work.