Concepts

Orgs

Orgs in Stubber

An Org is like a workspace where you keep everything for your organization — templates, stubs, articles, email layouts, contacts, and teams. You can have more than one org, and each org can have its own contacts and teams.

You can create your own org or be invited to join others. In each org, you might have different roles, which helps manage permissions and responsibilities.

# Creating an Org

When you sign up, you’ll go through a quick setup to create your first org. By default, you’ll also get a personal org.

You can create more orgs anytime by going to Manage → Orgs tab, found here.. On that page, you’ll also see all your existing orgs and their details.

# Adding a User to an Org

If you have the right permissions, you can add new people to an org in two steps:

1. Add them as a contact

   • Go to the Contacts tab in the Manage page.
   • Create the user by entering their name and at least one contact detail, usually their email address.

2. Add them to a team

   • Once they’re added as a contact, go to the Teams tab.
   • Add them to the team you want within the org.

When you add them to a team, they’ll automatically get an email invite. Both registered and non-registered users can be invited. If the person doesn’t already have an account, they’ll be asked to create one before they can join the org.

# Roles and Permissions

Each team in an org can be assigned its own permissions for creating, editing, and viewing templates, articles, contacts, teams, and orgs. This allows you to control exactly what a team can do with each type of resource.

To create a team, go to the Teams tab on the Manage page. From there, you can create a new team and assign its permissions.

When assigning permissions, you can enable or disable create, edit, and view permissions for each category—templates, articles, contacts, teams, and orgs. You can mix and match; for example, a team might only view contacts but create and edit templates.

Once a team is set up, you can add members to it. The permissions you set for the team will automatically apply to all its members, making it easy to manage what each user can do based on the team they belong to.

All teams can have a parent team, allowing you to create a hierarchy of teams within your org. This can be useful for organizing teams by function or project.

# Billing

Each stub you run in Stubber requires Stubbucks. Executing certain tasks or sending notifications consumes a set amount of Stubbucks, which are automatically deducted from your Org’s balance. For a detailed overview of how Stubbucks work, see the Stubbucks guide.

Because charges are applied at the time of execution, it’s important to ensure that your Org has enough Stubbucks available. If your balance is too low, Stubber won’t be able to complete the requested task or send the notification until additional Stubbucks are added.

Within each Org, you can manage your balance through the Billing* tab on the Manage page. From there, you can:

• View your current balance in real time
• Add Stubbucks directly to your Org manually or set up automatic top-ups
• Set up low-balance notifications and custom thresholds so you’re warned before running out

These features make it easier to stay on top of your usage and avoid interruptions.

You also have the ability to configure invoicing for your Org, allowing you to manage billing more effectively. You can set up billing details, and view past invoices.

# Usage

On the Usage page, you can see how many Stubbucks your Org has used over a selected date range. This page provides a clear breakdown of your spending so you can track and manage it effectively.

At the top of the page, you’ll find the total Stubbucks used for the chosen period. Just below that, the daily overview chart displays how your usage was spread across each day, making it easy to spot trends or unusual spikes.

Under the daily overview, you’ll find usage per template, which includes:

• Total stubs per template – the number of stubs run for each template.
• Average usage per stub – the average Stubbucks spent each time the template was used.
• Total usage for all stubs together – the combined Stubbucks used across all templates in the selected period.

Here’s what you can do on this page:

• Review total Stubbucks usage for the selected date range.
• Check the daily overview to identify trends or irregular usage days.
• Analyze template usage details to see which templates are most active and how efficiently they are running.
• Export or share usage data for reporting or planning purposes.
• Use these insights to adjust template settings or plan your future Stubbucks usage more effectively.

Regularly reviewing this page helps you maintain oversight of your Org’s spending and make informed decisions about managing templates and workflows.