Skip to lesson
Exit
Grok Bot identity, routines and permissions1 / 2

1 min lesson

Build a weekly report routine

Test one weekly report, turn it into a routine with clear limits and prove that its app access can be removed.

Step 1 of 2

Open the owning account's shared computer and connect only the two apps needed for the report. Complete the report once. Save the tested steps as a skill, then create a weekly routine with one owning Bot, named inputs, expected output, approval rule and missing-data response. Run it once and inspect its history. At project end, remove the routine, app sessions, connector authorization and report files, then verify each source.

From tested task to routine

Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.

diagram: flow

Schedule the work only after one complete run proves the steps and cleanup path.

Learn more

Full explanation

Shared computer, tested routine, mobile review, revocation

Run a weekly report across two apps, then remove its access
Shared computer, tested routine, mobile review, revocation
SayI want one Bot to prepare a weekly report from two signed-in apps. I also need to know what every other Bot can reach and how to remove access later.
DoSign in with the account that should own the work and open Agent Computer. Check the live access flow instead of relying on an old plan list.
SeeEvery Bot for that user shares the computer's files, browser sessions and command-line credentials. A separate Bot is not a separate security boundary.
DoConnect only the two needed apps and complete the report once. Save the tested steps as a skill, then create a weekly routine with its owning Bot, inputs, output, approval rule and missing-data response.
SeeThe routine shows its next run and can be tested, paused, edited and reviewed through its run history.
DoReview the same Bot and routine from a supported mobile surface. Close the app after sending one correction.
SeeThe same account, Bot, conversation, connectors and shared computer remain in use. Closing the app does not stop the cloud work or routine.
DoAt project end, pause or delete the routine, sign out of both apps, revoke their connectors in each source service and remove the report files from the shared computer.
SeeSource-system checks show that the sessions and connector access are gone. Deleting the Bot alone would have removed its profile, conversation and routines, but could have left shared-computer files and logins behind.
Learn more

Optional practice

Test yourself on Build a weekly report routine

QWhich result proves the weekly report routine is ready to keep?