Understanding Transposit

Frequently used terms in Transposit are as follows.

  • Activity. Activities coordinate people across work channels. Each activity has a feed of posts reflecting comments from users and updates to the state of the activity. Posts can be generated by scripts, service integrations, and direct user submissions. For details, see Using Activities.

  • Project. A project is a collection of people, assets, and workflows that allow users to get work done. A homepage for infrastructure.

    • To the user of a project, the project homepage is where requests can be made and the status of a project and its smaller components can be easily seen. These users may choose to subscribe to the project.
    • To the project engineer that is a member of the project, it is where they start their work. They create new types of requests, they manage an incoming queue of requests and incidents, and monitor the uptime and performance of their infrastructure.

    For details, see Setting Up Projects.

  • Script. Each activity can include a list of scripts defined by automated actions and triggering rules, including the ability to start a script manually or through a chat command. For details, see Using Scripts.

  • Template. A template holds the default fields and values for an activity, with scripts and triggering rules. All activities are created from a template. Each template is named and associated with a specific project and the provided fields, scripts, and todo items can be customized and extended. For details, see Setting Up Templates.

  • Runbook. Each template and activity can have a runbook of to do items which can be assigned to people. To do items are lightweight reminder items that can be controlled via the web page, over chat, or via a script. For details, see Creating Runbooks.

Next Steps#