Organizations & Teams

NotiGrid's organization system allows you to manage team access, share resources, and control permissions across your account.

Organizations

What is an Organization?

An organization is a workspace where you can:

• Share API keys and credentials
• Collaborate with team members
• Manage billing and subscriptions
• Control access permissions
• View unified analytics

Creating an Organization

Organizations are created automatically when you sign up. Each user starts with a personal organization.

Organization Settings

Access organization settings in Dashboard → Settings → Organization:

• Organization Name - Display name for your team
• Organization ID - Unique identifier for API requests
• Billing - Subscription and payment details
• Usage - Current plan usage and limits

Team Members

Inviting Members

1. Go to Settings → Team
2. Click Invite Member
3. Enter email address
4. Select role (see Roles below)
5. Click Send Invitation

The invited user will receive an email with an invitation link.

Member Roles

Owner

• Full access to all resources
• Can delete the organization
• Manage billing and subscriptions
• Invite/remove members
• Only one owner per organization

Admin

• Manage all resources except billing
• Invite/remove members (except owner)
• View all notifications and logs
• Create/edit templates and channels

Developer

• Create and send notifications
• View logs and analytics
• Create templates
• Manage API keys (read/write)
• Cannot invite members

Viewer

• Read-only access
• View notifications and logs
• View templates and settings
• Cannot modify anything

Role Permissions Matrix

Changing Member Roles

1. Go to Settings → Team
2. Find the member
3. Click Change Role
4. Select new role
5. Click Update

Removing Members

1. Go to Settings → Team
2. Find the member
3. Click Remove
4. Confirm removal

Removed members lose access immediately.

Projects

Projects help organize notifications within an organization.

Creating Projects

1. Go to Dashboard → Projects
2. Click New Project
3. Enter project details:
   • Name - Project identifier
   • Description - Optional description
   • Environment - Production, Staging, or Development
4. Click Create Project

Project Environments

Separate your workflows:

Production

• Live customer notifications
• High reliability
• Full feature access

Staging

• Pre-production testing
• Mirror of production setup
• Safe testing environment

Development

• Local development
• Experimentation
• No rate limits

Project-Specific API Keys

Create API keys scoped to specific projects:

1. Go to Settings → API Keys
2. Click Create API Key
3. Select Project
4. Choose project from dropdown
5. Set permissions
6. Click Create

Resource Sharing

Templates

Templates are shared across the organization. Any member with appropriate permissions can use any template.

Channels

Channel configurations (Slack, AWS, Twilio) are shared organization-wide.

API Keys

API keys belong to the organization. Members can create and manage keys based on their role.

Billing & Usage

Plan Management

Plans are managed at the organization level:

1. Go to Settings → Billing
2. View current plan and usage
3. Click Upgrade or Change Plan
4. Select new plan
5. Confirm changes

Usage Tracking

Monitor your organization's usage:

• Notifications sent - By channel and month
• API requests - Rate limit usage
• Active team members - Seats occupied
• Storage - Logs and data retention

Usage Alerts

Set up alerts for usage thresholds:

1. Go to Settings → Billing → Alerts
2. Click Add Alert
3. Configure:
   • Metric - What to monitor
   • Threshold - When to alert
   • Recipients - Who to notify
4. Click Save

Best Practices

1. Use Role-Based Access

Assign minimum necessary permissions:

• Give developers Developer role, not Admin
• Use Viewer role for stakeholders
• Limit Owner access to 1-2 people

2. Rotate API Keys

• Create project-specific keys
• Rotate keys when team members leave
• Use different keys per environment

3. Organize with Projects

• One project per application
• Separate staging and production
• Use descriptive names

4. Monitor Usage

• Set up usage alerts
• Review logs regularly
• Plan for growth

5. Document Team Access

• Maintain list of active members
• Document who has access to what
• Review permissions quarterly

API Access

Organization ID

Include your organization ID in API requests:

curl https://api.notigrid.com/v1/templates \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-Organization-ID: YOUR_ORG_ID"

Find your Organization ID in Settings → Organization.

Team Member Management via API

List team members:

GET /v1/organizations/{org_id}/members

Invite member:

POST /v1/organizations/{org_id}/members
{
  "email": "user@example.com",
  "role": "developer"
}

Update member role:

PUT /v1/organizations/{org_id}/members/{user_id}
{
  "role": "admin"
}

Remove member:

DELETE /v1/organizations/{org_id}/members/{user_id}

Security

Two-Factor Authentication

Require 2FA for organization members:

1. Go to Settings → Security
2. Enable Require 2FA
3. All members must enable 2FA to access

SSO (Enterprise)

Enterprise plans support Single Sign-On:

• SAML 2.0
• OAuth 2.0
• Google Workspace
• Microsoft Azure AD

Contact sales for SSO setup.

Audit Logs

View all actions taken in your organization:

1. Go to Settings → Audit Logs
2. Filter by:
   • User
   • Action type
   • Date range
3. Export logs for compliance

Migration

Transferring Resources

To transfer resources between organizations:

1. Contact support
2. Provide:
   • Source organization ID
   • Destination organization ID
   • Resources to transfer
3. Support will initiate transfer

Merging Organizations

To merge two organizations:

1. Contact support
2. Identify which organization to keep
3. Support will merge resources and billing

Support

Questions about organizations or teams?

• Email: support@notigrid.com
• Documentation: docs.notigrid.com
• Enterprise support: enterprise@notigrid.com