AMS
Request access

AMS · Connected business workflows

AI assistant — Ask in context. Stay in your workspace.

Use a conversational assistant to help with the AMS work you are authorized to access.

Who this helps

Signed-in teammates who want help finding or working with records they are permitted to access.

The situation

You remember the work you need but do not want to reconstruct where it sits in the workspace.

Fictional example: a teammate asks, “Find the Autumn launch project,” and sees an illustrative accessible result. This website example makes no live changes.

Follow the example, step by step

  1. Ask about your work

    What you do
    Ask the workspace assistant to find the Autumn launch project.
    What changes
    The request appears in the signed-in user’s assistant conversation.
    Why it helps
    You can describe the record you need without starting from a menu.
  2. Keep the request within available tools

    What you do
    Let the assistant use the tools enabled for your request and access.
    What changes
    The scene identifies workspace context as the basis for the response.
    Why it helps
    Assistance is tied to the capabilities available to that user.
  3. Read the returned context

    What you do
    Review the answer identifying the sample project and Forma Studio context.
    What changes
    The illustrative response names the project while its task card comes into view.
    Why it helps
    You can check that the assistant understood which work you meant.
  4. Decide the next action

    What you do
    Use the returned context to continue your work, checking any requested change before proceeding.
    What changes
    The accessible result remains beside the conversation.
    Why it helps
    The user can move from a question to an informed next step.

What your team gains

The user can start with a plain-language request and inspect the relevant workspace context.

Ask for help in the context of the workspace, with tools governed by existing permissions.

Inside AI assistant

Workspace conversation

Bring questions and actions into a conversational workflow.

Exposed AMS tools

Registered product tools give the assistant structured ways to work.

Permission checks

Tool availability and execution follow the relevant resource permissions.

Navigation context

Supported tools can point back to the relevant part of AMS.

Provider configuration

Use the AI provider configured for your workspace.

Distinct from agents

The assistant supports workspace work; brand agents handle configured customer-facing duties.

Questions and requirements

Can the assistant perform changes as well as find information?

Some exposed tools can make changes. Available operations and any required confirmations follow the tool, your permissions and workspace configuration; a chat response alone is not proof that an action completed.

Is this page making a real AI request?

No. The response is an illustrative website sample. Real assistant use requires a configured AI provider and the relevant access; usage charges and quotas depend on the setup. Customer conversations use the separate brand-agent workflow.

Requirements and limits

AI needs a configured provider. Available tools vary with permissions and configuration. The visual is a website explanation, not a recorded assistant execution.

Understand the next tool here

Read how each connection helps before choosing whether to open another page. Moving between tools does not itself configure an automatic handoff.

Projects & tasks — read how it fits

Continue in the project or task once you have identified the relevant work.

Give every task an owner, a deadline and the context to move forward.

Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.

Before you use it

Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.

Optional: explore the full Projects & tasks story ↗
Permissions & scopes — read how it fits

Understand the access that constrains available tools and records.

Control who can act, which project details they can change and what data they can see.

Fictional example: compare the displayed Project manager matrix with a Member view and assigned-record scope.

Before you use it

The displayed role matrix is an example, not the default of a named system profile. Access follows the configured project snapshot and applicable organization controls.

Optional: explore the full Permissions & scopes story ↗
AI agents — read how it fits

Choose a brand agent instead when the job is assisting customer conversations.

Give a brand agent the context to help with conversations and choose how it behaves on each channel.

Fictional example: the Autumn collection guide supports Instagram suggestions, while WhatsApp remains Off.

Before you use it

AI requires a configured provider; availability, quotas and provider charges depend on your workspace setup. AI responses can need correction. Auto mode is an explicit configuration, not the default behavior demonstrated here.

Optional: explore the full AI agents story ↗

Choose your starting point