Team Administration

Partners can create and manage multiple admin and staff users within their organization to collaborate effectively on device fleet management and customer support.

User Role Overview

Admin

Full access to all organization resources. Can manage other admins and staff.

Staff

Can view and manage all end-users and devices, but cannot manage other staff or admins.

User

End-users who can only access their own devices and data.

Adding Staff or Admin Users

Admin and Staff users are created the same way as regular users, but with a different role specified.

Create Admin User

Admins have full access to all organization resources:

curl -X POST \
  'https://app.podero.com/api/partners/v2.0/org/{org_id}/users' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer {auth_token}' \
  -d '{
    "role": "admin",
    "email": "[email protected]",
    "first_name": "Jane",
    "last_name": "Smith"
  }'

Create Staff User

Staff users can manage end-users but not other staff or admins:

curl -X POST \
  'https://app.podero.com/api/partners/v2.0/org/{org_id}/users' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer {auth_token}' \
  -d '{
    "role": "staff",
    "email": "[email protected]",
    "first_name": "Support",
    "last_name": "Team"
  }'

Email Invitation Flow

Create User with API

When you create an admin or staff user via the API, the user is created in the system.

User Receives Email

Your colleague will receive an email invitation to join the platform as an admin or staff member.

User Sets Password

They’ll use the invitation link to set their password and configure their account.

User Logs In

After setting up their account, they can log in and will have the appropriate permissions based on their role.

Make sure the email address is correct - the invitation will be sent to this address.

Permission Matrix

What Each Role Can Do

Administrator
Staff
Server-to-Server

Full Access

Action	End-Users	Buildings	Devices	Staff	Admins
Create	✅	✅	✅	✅	✅
Read	✅	✅	✅	✅	✅
Update	✅	✅	✅	✅	✅
Delete	✅	✅	✅	✅	✅

Admins can also:

Access organization settings
Manage API credentials
View all audit logs
Manage billing (via web portal)

Limited Admin Access

Action	End-Users	Buildings	Devices	Staff	Admins
Create	✅	✅	✅	❌	❌
Read	✅	✅	✅	✅	✅
Update	✅	✅	✅	❌	❌
Delete	✅	✅	✅	❌	❌

Staff can:

Manage all end-users and their devices
Provide customer support
View (but not manage) other staff and admins

List Team Members

Get all admin and staff users in your organization:

curl -X GET \
  'https://app.podero.com/api/partners/v2.0/org/{org_id}/users' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer {auth_token}'

Update Team Member Role

Change a user’s role (requires admin access):

# Promote staff to admin
curl -X PUT \
  'https://app.podero.com/api/partners/v2.0/org/{org_id}/users/{user_id}' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer {auth_token}' \
  -d '{
    "role": "admin"
  }'

Only administrators can change user roles. Staff users cannot promote or demote other users.

Remove Team Member

Delete a staff or admin user:

curl -X DELETE \
  'https://app.podero.com/api/partners/v2.0/org/{org_id}/users/{user_id}' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer {auth_token}'

Removing a user will revoke their access immediately. This action cannot be undone via the API.

Team Member Onboarding Checklist

When adding a new team member, follow this checklist:

1. Determine Role

Admin: For managers, senior support staff, or developers who need full access
Staff: For support team members who work with end-users daily

Consider the principle of least privilege - start with staff role and upgrade if needed.

2. Create User Account

new_member = create_user(
    org_id=org_id,
    role='staff',  # or 'admin'
    email='[email protected]',
    first_name='John',
    last_name='Doe'
)

3. Verify Email Sent

Confirm the team member received the invitation email. Check spam folders if needed.

4. Account Setup

Wait for the team member to complete account setup:

Set password
Configure profile
Accept terms of service

5. Training & Documentation

Provide team members with:

Access to this API documentation
Your internal procedures and workflows
Support escalation paths
Access to the Podero utility back-office web app

6. Verify Access

Have the new team member log in and verify they can:

Access the organization’s users and devices
Perform their assigned tasks
See appropriate menu options based on their role

Best Practices

Role Assignment

Use Staff role for day-to-day support operations
Reserve Admin role for managers and senior team members
Review roles regularly and adjust as responsibilities change
Document why each person has their assigned role

Security

Use company email addresses only
Require strong passwords (enforced by platform)
Remove access immediately when team members leave
Monitor for suspicious activity
Regular audit of active team member accounts

Collaboration

Use meaningful first/last names for easy identification
Create shared documentation for common procedures
Establish communication channels for the team
Define clear escalation paths for issues

Access Management

Maintain a list of all team members and their roles
Set up offboarding procedures for departing staff
Use external_user_id to link with HR systems if needed
Regularly review and remove inactive accounts

Common Scenarios

New Support Agent
Promote to Admin
Temporary Access
Team Member Departure

Scenario: Hiring a new customer support agent

# Create staff user for support
new_agent = create_user(
    org_id=org_id,
    role='staff',
    email='[email protected]',
    first_name='Support',
    last_name='Agent'
)

# Agent receives email, sets up account
# Can now help customers but cannot manage team

Scenario: Promoting a staff member to admin

# Staff member has proven capable, promote to admin
update_user(
    org_id=org_id,
    user_id=staff_user_id,
    role='admin'
)

# Notify user of promotion and new responsibilities
send_notification(
    staff_user_id,
    "You've been promoted to Admin. You now have full access."
)

Scenario: Consultant needs temporary access

# Create staff account for consultant
consultant = create_user(
    org_id=org_id,
    role='staff',
    email='[email protected]',
    external_user_id='temp_consultant_2024'
)

# Set reminder to remove access after project ends
schedule_reminder(
    date='2024-12-31',
    action='remove_user',
    user_id=consultant['id']
)

Scenario: Team member leaves the company

# Immediate steps
delete_user(org_id, departing_user_id)

# Document and audit
log_user_removal(
    user_id=departing_user_id,
    reason='Employment terminated',
    date=datetime.now(),
    removed_by=admin_user_id
)

# Reassign their responsibilities
reassign_open_tickets(
    from_user=departing_user_id,
    to_user=replacement_user_id
)

Web Portal Access

While the API provides programmatic access, team members should also use the Podero utility back-office web app for day-to-day operations.

Web Portal Features

Dashboard: Overview of all users and devices
User Management: Search, filter, and manage end-users
Device Fleet View: Monitor all connected devices
Support Tools: Quick access to reconnection URLs and troubleshooting
Team Management: View team members (admins can manage)
Settings: Organization configuration and API credentials (admin only)

Access the Web Portal

Production: https://app.podero.com/accounts/login/
Sandbox: Your unique sandbox subdomain URL

Next Steps

User Management

Learn about managing end-users

API Reference

Complete user parameter reference

Authentication

Set up API access for your team

Overview

Getting Started

End-User Workflows

Back-Office Workflows

API Reference

Heat Pumps

Electric Vehicles

Solar Inverters

Team Administration

Team Administration

User Role Overview

Admin

Staff

User

Adding Staff or Admin Users

Create Admin User

Create Staff User

Email Invitation Flow

Permission Matrix

What Each Role Can Do

List Team Members

Update Team Member Role

Remove Team Member

Team Member Onboarding Checklist

Best Practices

Common Scenarios

Web Portal Access

Web Portal Features

Access the Web Portal

Next Steps

User Management

API Reference

Authentication

Overview

Getting Started

End-User Workflows

Back-Office Workflows

API Reference

Heat Pumps

Electric Vehicles

Solar Inverters

​Team Administration

​User Role Overview

Admin

Staff

User

​Adding Staff or Admin Users

​Create Admin User

​Create Staff User

​Email Invitation Flow

​Permission Matrix

​What Each Role Can Do

​List Team Members

​Update Team Member Role

​Remove Team Member

​Team Member Onboarding Checklist

​Best Practices

​Common Scenarios

​Web Portal Access

​Web Portal Features

​Access the Web Portal

​Next Steps

User Management

API Reference

Authentication

Team Administration

User Role Overview

Adding Staff or Admin Users

Create Admin User

Create Staff User

Email Invitation Flow

Permission Matrix

What Each Role Can Do

List Team Members

Update Team Member Role

Remove Team Member

Team Member Onboarding Checklist

Best Practices

Common Scenarios

Web Portal Access

Web Portal Features

Access the Web Portal

Next Steps