Before you begin
Gather the following before you start so you’re not interrupted mid-setup:- Admin credentials for your identity provider — required only if you plan to enable Single Sign-On (SSO). You’ll need access to your IdP’s admin console to supply metadata and verify the connection.
- A list of teammates to invite — even a short pilot list of five to ten people is enough to validate your setup before a wider rollout.
- A few decisions made in advance:
- Workspace name — this appears in notifications, emails, and shared links, so pick something meaningful to anyone who might see it.
- Default timezone — used for scheduling, reporting, and activity timestamps across the workspace.
- Project visibility default — decide whether new projects should be private (invite-only) or visible to all workspace members by default.
If any step in this guide depends on your IT team — such as DNS changes for a custom domain, SSO metadata exchange, or firewall rule updates — don’t wait. Proceed with the other steps in parallel so you’re not blocked while those changes are in flight.
Setup steps
Create your organization
Sign in to Storm at app.storm.io. If this is your first time signing in, Storm automatically prompts you to create a new organization. Follow the on-screen setup wizard to get started.When choosing your organization name, keep in mind that it appears in notification emails, shared project links, and any external-facing activity summaries. Avoid internal codenames or abbreviations if external collaborators — clients, contractors, or partners — will ever be invited to your workspace. A clear, recognizable name prevents confusion and looks professional from day one.Once you confirm the name, Storm provisions your workspace and drops you into the main dashboard. You’re now ready to configure it.
Configure general settings
Navigate to Settings → General from the left sidebar. This is where you control the core defaults that apply to every new member and project created in your workspace.Configure the following:
Members can override the timezone and display preferences in their own profile settings, but what you set here becomes the baseline for everyone who joins after you save these values. Take a moment to get them right — changing the timezone later can cause confusion in historical reports and scheduled workflows.
| Setting | What it controls |
|---|---|
| Workspace name | The display name shown across the UI, emails, and notifications. |
| Timezone | The default timezone used for timestamps, scheduled reports, and activity feeds for new members. |
| Display preferences | Date format, number format, and theme defaults for new accounts. |
Invite teammates
Navigate to Settings → Users and select Invite members. Enter each person’s work email address and assign them a role before sending the invitation. To invite many people at once, use the Import CSV option on the same page — prepare a CSV file with the columns
Start with a small pilot group of five to ten people before inviting your entire organization. This gives you a chance to validate your settings, test any SSO or directory sync configuration, and collect early feedback before a wider rollout. You can always invite more people later from the same Settings → Users page.
email, role, first_name, and last_name, one member per row.Storm offers three built-in roles:| Role | When to use it |
|---|---|
| Admin | Trusted teammates who need full access to workspace settings, billing, and all projects. |
| Member | Most of your team — can create and manage projects but cannot access billing or workspace settings. |
| Viewer | Stakeholders or clients who need read-only visibility into specific projects. |
Set up your first project
From the main dashboard, select New project. Give your project a clear, descriptive name and add a short description — both are searchable and help teammates understand the project’s purpose at a glance.After creating the project:
- Add initial members — you can add a subset of your workspace members and assign project-specific roles that can differ from their workspace-level role.
- Configure project settings — set the default visibility, notification preferences, and any project-level integrations.
- Use it as a sandbox first — before you standardize a template for the rest of your organization, run a real workflow through this project to identify any settings you want to adjust. What works in theory often needs a small tweak in practice.
Next steps
Now that your workspace is up and running, explore these resources to deepen your understanding and unlock more of Storm’s capabilities:- Key Concepts — understand the core building blocks (workspaces, projects, roles, and API credentials) that underpin everything in Storm.
- Workspace Settings Reference — a full reference for every setting available in the General, Security, and Notifications panels.
- Roles and Permissions — learn how workspace-level and project-level roles interact, and how to configure custom roles on higher-tier plans.