OdyCust/ GUIDE
УКР

Member groups

Organize the team and share selected resources without granting operation permissions.

What a group contains

A group has a stable identifier, name, description, status, version and members from one organization. It is an organizational list, not a role or an approval quorum. A resource owner may share a private Wallet, Address or AddressGroup with this group through the API. Current active group membership then participates in resource access; renaming preserves that access, while removal or group disable removes this grant.

Management after interface adoption

The backend has separate read, create, update and membership-replacement operations with explicit permissions. The current console does not expose them; there are no corresponding Team buttons yet.

Membership replacement and conflicts

A membership change supplies the complete desired list and current version. If someone else changed the group, reread it and compare the member list before confirming again.

What a group does not change

Adding a member does not grant a role, signing permission or access to funds. Removing a member does not replace the access-disable procedure. Group membership administrators can change who sees resources shared with the group. Treat groups.manage_members as security authority; the recipient still needs the normal RBAC permissions.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

Search stays within this guide. It does not request console data.