First 15 Minutes
This checklist walks a new admin through the minimum steps needed to get Robost operational for a pilot group. Follow the steps in order — each one builds on the previous.
Checklist
Section titled “Checklist”1. Sign in
Section titled “1. Sign in”Go to app.robostai.com and sign in with the credentials provided during onboarding. If you are the first admin for your organization, your account was created by the Robost team during provisioning.
2. Verify your organization settings
Section titled “2. Verify your organization settings”Navigate to Configure in the left sidebar and confirm your organization name, contact details, and seat allocation are correct. This is also where you can review your current plan and usage quota. If anything looks wrong, contact support before proceeding.
3. Authentication
Section titled “3. Authentication”Robost currently uses email/password authentication. SSO is on the roadmap — contact support if SSO is a requirement for your deployment. Do not proceed to the next step until all admin accounts have working login credentials.
4. Review the default detection policies
Section titled “4. Review the default detection policies”Robost ships with a set of default policies that cover common sensitive data scenarios across all monitored applications. Navigate to Configure → Scenarios to review them. For each policy, confirm the action (Monitor, Warn, or Block) is appropriate for your organization’s risk tolerance. If you need to adjust or add policies, see Policies → Creating a Policy. At minimum, verify that your highest-risk detection types — source code, PII, payment data — are set to Warn or Block rather than Monitor.
5. Deploy the extension to a pilot group
Section titled “5. Deploy the extension to a pilot group”Do not roll out to the full organization on day one. Start with 20–50 users: your security team plus a small group of volunteers from a business department. Follow the deployment instructions in Extension → Overview to push the extension via Chrome Enterprise or your MDM platform. Managed configuration (API base URL and enrollment token) is pushed alongside the extension so users are enrolled automatically with no manual steps.
6. Wait for the first alert
Section titled “6. Wait for the first alert”Once pilot users start their normal working day and interact with AI tools, alerts typically appear within 24 hours. You can watch the Insights dashboard for incoming detection counts. If no alerts appear after a full working day of pilot activity, check that the extension shows “Enrolled” status in the popup and that the managed configuration was delivered correctly.
7. Investigate your first alert
Section titled “7. Investigate your first alert”When an alert arrives, open it in the Alerts Inbox and review the detection type, the application involved, the employee, and the action that fired. If you need guidance on what to look for and how to triage, see Alerts → Investigating. Use the thumbs-up / thumbs-down feedback buttons to flag false positives — this helps you tune your policies before the wider rollout.