مرکز اسناد در حال تکمیل است — وضعیت حقوقی هر سند را پیش از استناد بررسی کنیدمشاهده اسناد
لوگوی رسمی ارث‌کوپ مرکز دانش ارث‌کوپشناخت · راهنما · اسناد بنیادین
فاتغییر زبان
فارسیفعال Englishراهنماهای انگلیسی العربيةترجمه موجود نیست
EarthCoop.ir

English Product Guides

System Groups and User-Created Groups

Before creating anything new, distinguish system groups from user-created groups.

System groups are automatic

EarthCoop materializes system groups from canonical member dimensions. A member does not create a public assembly, professional/specialty group, or age/gender group through an ordinary “new group” form simply because one is missing from their dashboard.

System membership comes from verified profile data such as:

  • Primary Residence and the applicable governance topology;
  • profession/occupation;
  • expertise/specialty;
  • age/gender dimensions used by the system.

When the relevant system group does not yet exist, EarthCoop can create/materialize it as part of the canonical membership process. This prevents duplicate unofficial groups from being mistaken for the official system structure.

User-created groups are separate

Where the product exposes user-created groups, they serve member-created organizational purposes such as a union, organization, company or other initiative. They do not replace official system groups and they do not inherit public-governance authority merely because their membership overlaps with a public assembly.

A user-created group's membership and management rules belong to that group's product contract. They must not be used to rewrite a member's canonical Primary Residence or system-group eligibility.

Managing an official system group

Holding a Manager responsibility in a system group does not mean the Manager owns the group or may arbitrarily redefine its official identity. Canonical name, scope, governance level, dimension and eligibility come from EarthCoop's system data and policy.

Manager/Inspector powers should therefore be understood as delegated responsibilities inside the current platform rules, not as a right to convert a public assembly into a private community or to manually assign official election eligibility.

Roles are not free-form labels

The current role vocabulary includes Observer, Active, Inspector, Manager, Guest and Temporary Active. Role meaning is enforced by domain rules.

In particular:

  • Temporary Active can allow limited participation where policy permits but does not create systemic-election voting/selectability rights;
  • Inspector and Manager retain the personal systemic voting/selectability rights attached to their elected member status;
  • Observer membership at higher levels does not become Active simply because the group grows;
  • official responsibilities and representation are applied through their relevant election/appointment rules, not arbitrary role editing.

Invitations and membership

EarthCoop also has invitation mechanisms at the account/product level, but an invitation code for registration should not be described as a universal mechanism for taking control of official system-group membership. System memberships are derived from canonical member dimensions.

For how membership is resolved, see Membership in Groups. For residence-governance membership, see Location & Governance.

Older documentation that described system groups primarily through Public/Private visibility, manager-generated invitation codes, or manually promoted official roles represented a legacy/generalized model. Current documentation separates system governance from user-created organizations.