Review the new supplier
- Supplier
- Northstar
- Your role
- Purchasing lead
- Next step
- Review documents
Your team’s ruleA purchasing lead must confirm before approval.
Needs your confirmation
Agentic Workspaces
Bring your people, AI-powered apps and guided processes together—with shared context, defined permissions and AI resources chosen for the work.
What makes it agentic? AI can carry out tasks: handle requests, update information and move work forward within the rules you define.
My work
Morning, Maya.
One case needs your attention.
Your team’s ruleA purchasing lead must confirm before approval.
Needs your confirmation

The next step, the context and the rule.
Together, where the work happens.
A place for everyday work
Your team enters the workspace to do the work. People find the apps and processes assigned to them, see cases needing their role, and pick up where they left off.
Make requests, work with information and take the actions your role allows. Amy runs supported behavior from the rules your team has defined.
How Amy runs your appsFollow a case through its decisions and handoffs. See what needs you, what is waiting and what has been completed, with recorded history to look back on.
Find people in the team directory and talk through the work in private, one-to-one messages. The team has a shared place to return to.
AI does the work. On your terms.
Give people a clear place to use AI, with responsibilities and access defined before they begin.
Workspace owners invite people and assign their app and process roles. Using the work and changing its underlying instructions are separate permissions.
Owners manage shared AI model connections. Deployment administrators allow or block models for modelling and app use.
Define the decisions that need a person. Amy checks app permissions and supported data changes; guided processes use assigned roles and explicit confirmations.
Authorized users can inspect recorded app activity and process history. Deployment administrators review model calls, token usage and estimated costs.
Owners manage people and settings in Amy’s authoring area. Team members enter the workspace to use the apps and processes available to them.
Start with work you know
Bring the person who knows the work. You can begin with a clear process model and decide together what AI should take on.
Describe the task, its exceptions and the decisions that need a person. Review the understanding Amy captures.
Shape an app or guided process. Configure access and AI resources, then try the behavior before making it available.
Invite colleagues and assign their roles. They enter the workspace to find and use the work available to them.
A few practical questions
How the workspace fits the way you create, share and use AI with Amy.
Amy runs supported agentic apps directly from their intent. You configure the work, access and AI resources and try the behavior, without a separate app codebase to build or deploy. See how execution works.
People can use the apps and processes assigned to them without authoring access. The people responsible for defining the work review and change its intent in Amy’s authoring area.
Amy helps collaborators define and refine reusable AI instructions. Take the finished prompt to your chosen AI tool, where execution and access follow that tool’s controls. Explore shared prompts.
Shared context means the relevant rules and information available to an app or process. One-to-one messages remain between the two people in the conversation; Amy does not read them.
Your team’s Agentic Workspace