Configuring Transposit

When beginning to understand Transposit, it's helpful to know the high-level functionality made available to you and the sequence of tasks in which you'll typically be configuring its toolbox of features, after setting up Transposit, as outlined below.

  1. Create activity types. When team members are discussing an incident or task in many places, you would like a single source of truth. An activity is a container for everything that relates to the incident or task, producing a timeline that defines a knowledge stream with an audit trail of everything that happens in its context. Get started here to configure existing activity types, such as incidents and tasks, and get started here to create new activity types, such as requests and jobs.

  2. Create runbooks. Do this to document your processes, such as when you want to remember the set of steps you took to resolve that last activity, so that anybody would be able to replicate that process when the need for the same or a similar incident or task arises again. Click New runbook to get started and add steps with titles and descriptive text explaining what to do.

    • Incrementally automate runbook actions. Add some automated actions to simplify the process, make it more reliable, and reduce manual toil. Get started here and discover that most of the actions you'll want to automate are just a simple API call away.

    • Add runbook triggers. It would automate your processes even further if you would be able to start runbooks automatically when an activity of a certain type happens, otherwise, a new person in the process would not know which runbooks they should be following. Get started here so that, for example, the creation of a Jira ticket or a conversation in Slack will automatically cause your runbook to be initiated.

Now that you have a high-level overview of everything you can do with Transposit, let's see how it is used.

Next Steps#