Manage Organization Members

Overview

Organizations in the Regen App make it easy for teams, companies, and institutions to work together on ecological projects. Each organization provides shared access to projects, credits, and resources through role-based permissions, allowing you to assign exactly who can view, edit, or manage each part of your organization’s work.

Behind the scenes, every organization is backed by a DAO (Decentralized Autonomous Organization) using DAO DAO smart contracts. This structure provides secure, transparent control of on-chain assets and permissions — but you don’t need to understand the blockchain details to use it. The Regen App provides a simple interface for adding members, assigning roles, and managing access.

1. Understanding Organization Roles

Each member of an organization is assigned a role that defines what they can do across the organization and its associated projects.

All roles, except Viewer, require a Keplr wallet and a Regen address so they can perform on-chain actions.

Role

General Description

Owner

The creator and ultimate controller of the organization. Cannot be removed except by transferring ownership.

Admin

Manages team members, funds, and projects. Shares most permissions with the Owner but can be removed by the Owner or other Admins.

Editor

Can edit organization content and projects but cannot manage members or funds.

Viewer

Has read-only access to the organization and its projects. No wallet required unless permissions are upgraded.

2. Role Details and Permissions

Owner

  • Has full administrative control of the organization.

  • Can add, edit, and remove members, manage credits, and edit projects.

  • Controls organization-level actions such as:

    • Creating or updating credit classes.

    • Managing the organization’s credit portfolio (send, retire, sell).

    • Managing project creation and metadata.

  • Cannot be removed from the organization unless they transfer ownership to another member.

  • Automatically has access to all projects under the organization.

Admin

  • Has nearly the same permissions as the Owner but can be removed or modified by the Owner or other Admins.

  • Can:

    • Manage team members and their roles.

    • Create and manage projects.

    • Manage credits, credit classes, and sell orders.

    • Edit organizational profile information.

  • By default, Admins have access to all projects within the organization, though this can be restricted at the project level.

Editor

  • Focused on project and content management rather than administration.

  • Can:

    • Edit the organization’s profile (name, description, logo, etc.).

    • Edit project content where they have project-level edit rights.

  • Cannot manage members, funds, or credits.

  • Editors automatically gain access to all projects by default but can have that access revoked or restricted by Admins or the Owner.

Viewer

  • Read-only role for people who need visibility but not control.

  • Can:

    • View all organization projects and the credit portfolio.

    • See project and credit details, including private information where permitted.

  • Does not require a wallet address until upgraded to a higher role.

  • Useful for external partners, clients, or buyers who need to review data but not participate in management.

Please note, by default project credits are issued to the Organization's account. If you want to have Admins who are not part of the Organization manage the project credits, you will need to manually send the credits to the project account.

3. Default Access and Inheritance

When you add someone to your organization, their role determines their default access to all projects.

  • Owners, Admins, and Editors automatically have access to every project associated with the organization.

  • Viewers do not automatically receive project access — they must be added explicitly if needed.

  • Admins and Editors can have their access revoked from specific projects to limit their visibility or editing rights.

If an Admin or Editor adds a new member, that new member inherits project permissions only for the projects the adding Admin has rights to. This ensures that access cannot be granted to projects an Admin doesn’t control.

4. Adding Members to the Organization

  1. Go to your Organization Dashboard in the Regen App.

  2. Open the Members tab.

  3. Click Add Member.

  4. Enter the member’s Regen address (for Owner, Admin, or Editor) or email address (for Viewer or non-wallet roles).

  5. Choose their role.

  6. Confirm to send the invitation.

If the invitation is by email, the user will receive a link to join and can later connect a wallet if their role is upgraded.

All role assignments and invitations are logged within the organization’s DAO and can also be viewed or managed directly through the DAO DAO app at daodao.zone.

5. Changing or Removing Members

Changing Roles

  • Owners and Admins can upgrade or downgrade a member’s role.

  • Changes automatically cascade to projects where that Admin has rights.

  • Project Owners retain their project ownership regardless of organization-level changes.

Removing Members

  • Owners and Admins can remove members from the organization.

  • Removal cascades to all projects the removing Admin has rights to.

  • The Owner cannot be removed; ownership must first be transferred.

  • Admins can only remove members from projects they control — complete removal may require coordination between multiple Admins or the Owner.

All member changes are recorded on-chain, ensuring transparent access tracking.

6. Managing Members Through DAO DAO

While the Regen App provides a simplified interface, all member management is ultimately powered by DAO DAO’s role-based authorization module (RBAM). Through daodao.zone, organization members with Admin or Owner roles can:

  • View and modify all roles and authorizations.

  • Create or update governance proposals.

  • Manage on-chain assets, treasuries, and subDAOs.

  • Execute or delegate on-chain actions directly.

This enables more advanced and auditable operations while the Regen App remains user-friendly for everyday tasks.

7. Best Practices for Role Management

  • Limit Admin access to trusted members who need control of credits, funds, and membership.

  • Use Editor roles for team members who contribute content or manage projects but don’t need admin rights.

  • Use Viewer roles for external stakeholders, buyers, or auditors who need to see private project data.

  • Review roles regularly to maintain security and transparency.

Summary

Organization member management in the Regen App provides a clear, flexible structure for collaboration:

  • Roles define permissions and access across the organization and projects.

  • Owners, Admins, and Editors have broad access by default, but permissions can be refined.

  • All changes are transparent and secure, managed through DAO DAO’s on-chain infrastructure but controlled through a familiar, intuitive interface.

PreviousCreate an OrganizationNextManage Project Collaborators

Last updated

Was this helpful?