Skip to content

Managing Members

SipPulse AI structures its operations around organizations and users. Every user must be part of an organization. When a new user signs up, they simultaneously create an organization account and become its owner. This user has all permissions for managing the organization.

User Roles

There are three roles available for users within an organization:

Owner

  • Role: Founder of the organization.
  • Permissions: Full permissions to manage the organization.
  • Restrictions: Cannot be removed or have their role changed. Each organization can only have one owner.
  • Future Consideration: There may be a future update to allow the transfer of the owner role to another user.

Administrator

  • Role: Manages the organization similar to the owner.
  • Permissions: Full permissions to manage the organization.
  • Restrictions: Can be removed or have their role edited.

Member

  • Role: User with access to platform resources.
  • Permissions: Can use the platform's features but cannot manage organizational settings.
  • Restrictions: Cannot manage users, billing, or organizational settings.

Note: A "Guest" role, which will allow read-only access, is under development.

Adding a New Member

To add a new member to your organization:

  1. Navigate to the Members page.
  2. Click on the Add User button.
  3. Fill in the required information: name, email, and a temporary password.
    • The temporary password will be sent to the user's email, prompting them to change it. Ensure you use a strong password or click the Generate Password button for security.
  4. You can disable the email notification, but this is not recommended. If disabled, you will need to manually provide the password to the user.

Editing a Member

Currently, you can only edit the role of a member. For other changes like name and password, the member must manage their own details.

  1. Navigate to the Members page.
  2. Click the edit icon next to the member whose role you want to change.
  3. Update the role as needed.
  4. Save the changes.

Removing a Member

To remove a member from your organization:

  1. Navigate to the Members page.
  2. Click the trash icon next to the member you wish to remove.
  3. Confirm the removal action in the prompt.

Note: Removing a member will revoke their access to the organization's resources and data.

User and Organization Relationship

  • Financial Management: All financial activities are linked to the organization. When an administrator or owner adds credits, all users within the organization have access to these credits for API calls.
  • Resource Access: Any resource created by a user (e.g., instances or agents) is accessible to all users within the organization.
  • Usage Tracking: Each user's activities are tracked and displayed on the dashboard, showing who utilized specific credits and resources.

Best Practices for Managing Members

  • Regularly Review Membership: Periodically review the list of members to ensure that only active users have access.
  • Update Roles as Necessary: Adjust member roles based on changes in their responsibilities within the organization.
  • Enforce Strong Password Policies: Ensure that all members follow strong password policies to maintain the security of the organization's data.

Troubleshooting

Common Issues

  • Member Not Receiving Email: Ensure that the member's email address is correct and that the email was not marked as spam.
  • Unable to Edit/Remove Member: Verify that you have the appropriate permissions to perform these actions.

FAQ

How do I change a member's role?

Navigate to the Members page, click the edit icon next to the member's name, and select the new role from the dropdown menu. Save the changes.

Can I disable a member's access without removing them?

Currently, the only way to revoke a member's access is by removing them. In the future, there may be an option to temporarily disable a member's account.

What happens to a member's data when they are removed?

Removing a member does not delete their data. Any resources or instances created by the member will remain accessible to the organization.