SupportOpen Kimpton

Workflows

Set up a repeatable task and find its results.

A workflow starts a task, gathers any selected data, asks Kimpton to work on it, and saves the result. It can run when you choose Run now, on a supported schedule, or when a selected market event occurs. Some specialist reports are manual only; check their availability.

For example, you could ask Kimpton to review new filings for a chosen portfolio and email a summary. The event trigger needs an Enterprise FactSet market-data connection. A simpler first workflow can start on a schedule and summarize an available Vault document.

  1. Open Workflows and create a draft.
  2. Check its trigger, data, prompt, and Notify destinations.
  3. Run a test. Read the result and check its sources.
  4. Publish only when the result and delivery settings are right. Pause a published workflow to stop automatic runs.

Each run is saved in History. A saved result and a delivered message are different; check both. Runs may use credits, so review the estimate and schedule before publishing.

Share a workflow

New workflows start with General Access: Restricted, so only the people listed in Share can open them. A Restricted workflow is private even from organization owners and admins: they see it only if it is shared with them. Open Share, search Add people, and choose Viewer, Editor, or Owner for each person. To change the role of someone who already has access, choose a role next to their name; the row shows their previous role until you select Share. A workflow can have several Owners and always has at least one: the last Owner cannot remove themselves or choose another role, so make someone else an Owner first. To open the workflow to the whole organization, change General Access to Everyone in your organization. Everyone in the organization can then view and run the published version. Any Owner can make this change; it does not need an admin. People you added as Editor or Owner keep that role. Changes in the Share dialog wait until you select Share; Cancel discards them. Everyone opens the same workflow page; only the available actions differ. Viewers see the published steps with their settings read-only, select Run to run the published version, and open published runs and results from History. Editors can also change the draft, test, and publish, and see test runs. Owners can also manage sharing (add and remove people, change roles, and set General Access) and archive or delete the workflow; Editors cannot manage sharing. Organization admins can do what an Owner can for workflows shared with everyone in the organization.

Someone you add to Notify gets Viewer access when you publish or run the workflow, if they do not already have access. Until then the Notify block shows Will be added as Viewer under their name. Only an Owner or an organization admin can give access this way; an Editor can add only people who already have access to Notify. Removing a Viewer removes them from the draft's Notify destinations. When you remove a Viewer from Notify, Kimpton asks whether to also remove their access: choose Remove access or Keep access. A Slack channel destination gives no person workflow access.

When you share a workflow, any personal Vault documents, Vault skills, or Kimpton portfolios it references are also shared read-only with the same audience. Review the Also shared with list in the Share dialog; the button then reads Share with N items. Drafts always save; people and items are shared only when you publish or run, and publishing asks you to confirm any items with Publish and share. The items remain in their original workspace and keep their owner. Removing workflow access does not revoke those item grants. Personal connections cannot be used by a workflow that is shared or delivers to someone other than its owner; ask an admin to connect the provider for the organization.

For a personal Vault folder, the preview includes its current documents. A shared run can use up to 50 personal Vault documents and skills, counting each selected folder's current documents. If the selection exceeds that limit, choose fewer documents or move the folder into the organization workspace.

The Workflows list shows each workflow's primary owner and its status: Draft until a version is published, then Live. The workflow's page shows the same status. Use the All, Owned by me, and Shared with me filter to narrow it; All is the default. Owned by me lists every workflow you are an Owner of. Shared marks a workflow shared with everyone or with specific people; hover it to see which. A private workflow has no marker. For a workflow with no published version, its steps are labelled as the draft and History lists test runs of the draft, which only people who can edit see.

Shared workflows and workflows that deliver outside the owner use organization data plus their explicitly referenced shared items. They cannot read the owner's other personal data. A manual run uses the triggering member's credits; a scheduled run uses the primary owner's membership to run. The primary owner is the person who created the workflow, until they leave its Owners: then the longest-standing other Owner becomes primary owner.

When a Kimpton platform admin uses view as for a specific member, Workflows shows what that member can access, including their Restricted workflows. This view is read-only: the admin sees the same workflow page with every control disabled and can inspect workflows, runs, results, files, and People with Access for workflows the member manages, but cannot create, edit, run, share, or delete workflows. The admin must choose a member before opening Workflows from an organization-only view.

On this page