Enabling stories for Workbench
As explained in an Introduction to Workbench, the product is user-scoped. Any builder within a team can enable a story for Workbench via the send-to-story settings in the build pane. There are two options for stories and Workbench:
Workbench: this means the story is only available to use in Workbench, not other stories. These stories do not count towards your tenant limits as they cannot run autonomously.
Workbench and send-to-story: this means it can be referenced in either Workbench or another Story. This is great if you’re looking to leverage existing stories in Workbench as well. These do count towards your tenant limits.
Finding optimal efficiency with Stories and Workbench
With Workbench, you are in the driver's seat. You determine what Workbench can and cannot do within your tenant based on the stories you enable.
For ideal functionality, make sure your send to story inputs are well-defined with descriptions. The stronger a story description, the better Workbench will understand your task and perform your request. This is especially helpful when you have similar stories available to Workbench.
Looking for inspiration?
Workbench is useful to any team! Here are a few ways different teams can take advantage of the product
Security: enrich user and asset information, investigate EDR alerts, analyze and block IPs, domains, and URLs, run real-time response and forensic investigations
IT: create a ticket in Jira, lock down a device in Jamf
Any Tines builder: view upcoming meetings, send a Slack message, create a new document in Google Docs
If you need inspiration, explore our Library. We’ve added a few stories that you can import into your own tenant. Each story includes a complete look at the chat conversations to give you an idea of what the output may look like.