Members

source-coop member manages the members of an organization (ACCOUNT) or a product (ACCOUNT/PRODUCT). source-coop invitation answers the invitations that you receive. A member's name is their account ID. You cannot invite by email.

Roles, from most to least access: owners, maintainers, write_data, read_data.

• Only owners can make a member an owner, or change or revoke an owner.
• Owners and maintainers can manage the other roles.
• A product's member list shows only the product's own members. The organization's members can also use its products, and show in the organization's list.

With shell completion, TAB shows:

• For ACCOUNT or ACCOUNT/PRODUCT: your organizations and their products.
• For a member: the members of that organization or product.
• For invite: the organization's members who are not yet members of the product.
• For invitation accept, reject and member leave: your invitations and memberships.

With --json, these commands print the memberships as the API gives them: membership_id, account_id, membership_account_id, product_id (for a product), role, state and state_changed. invite --json prints an array of the new memberships.

create and delete are other names for invite and revoke.

List and view

# members and open invitations
source-coop member list my-org

# the members of a product, as JSON
source-coop member list my-org/my-data --json

# only open invitations
source-coop member list my-org --state invited

# move through the members full screen
source-coop member list my-org -i

# one member; -i for its screen
source-coop member view my-org alice

member list -i uses the same keys as product list -i. On a member's screen:

• e changes the role.
• d revokes the membership. For an invitation, d withdraws it, and e is not available.
• b opens their profile.

Invite

# invite two accounts to an organization
source-coop member invite my-org alice bob --role maintainers

# invite each account listed in a file to a product
source-coop member invite my-org/my-data -A people.txt --role read_data

# asks who to invite, and the role
source-coop member invite my-org

invite takes account IDs as arguments.

• --accounts-file PATH (-A, - for stdin) adds one ID from each line. It skips empty lines and lines that start with #.
• --from-file reads account_id and role from a JSON object.
• Each account gets its own invitation. If the API refuses one, the CLI shows the error and sends the others. Then the command fails.
• At a terminal, invite asks for the missing accounts and role, and then asks you to confirm. The default role is read_data. It shows owners only if you can give that role. ← goes back one question.
• If invitations fail, the CLI saves the ones not sent as a draft. The next invite to the same place offers them again.
• If you invite a service account of the product's owner, it becomes a member at once. Its role must be read_data or write_data.

Edit

# give a member another role
source-coop member edit my-org alice --role owners

# select a member, then a role
source-coop member edit my-org -i

Without --role, edit asks for a role, starting from the current one. You cannot change the role of an invitation. Revoke it and invite again.

Revoke and leave

# also withdraws an open invitation
source-coop member revoke my-org alice

# end your own membership
source-coop member leave my-org

revoke asks you to confirm. For your own membership, you must also type the organization or product name.

leave always asks you to type the name, because only an owner or maintainer can add you again.

Without a terminal, revoke and leave need --yes.