Appearance
Organization settings
Organizations have their own page in the dashboard, reached from Organization → Settings in the sidebar. It holds defaults applied to repositories as they arrive, and it is the only settings surface that is not per repository.
Choose an organization first
Organization settings and members are unavailable while All organizations or a personal account is selected.
The page applies to the organization currently chosen in the organization switcher at the top of the dashboard. Choose one:
- with All organizations selected, the page says Select an organization in the switcher above to edit its settings;
- for a personal account, it says Personal accounts don't have organization-level settings. Personal installations have repository settings only.
Who can change them
Only admins of that organization. Members see the page with a View only badge and disabled controls, plus the notice You have view-only access to this organization's settings. Ask an admin to make changes. The repository settings page shows the same notice, adding You can still view and trigger reviews.
Changes are drafts until you press Save Changes; Cancel discards them.
Active settings
| Setting | Default | Effect |
|---|---|---|
| Enable review for new repositories | on | Whether Enable AI review on Pull Requests starts on for a repository the first time it appears in the dashboard. Existing repositories are unaffected; use their own repository settings. |
| Data retention (days) | 90, or your plan's limit if lower | How long review history is kept before it is deleted. You can lower it, or raise it up to your plan's limit. See Data and privacy. |
Members
Organization → Members in the sidebar lists everyone linked to the organization's installation: their avatar and display name, GitHub username, email where known, and role. The person who installed the app is tagged · installer.
The installer appears first in the list, followed by other members in username order.
Like the settings page, it needs an organization chosen in the switcher; personal accounts show Personal accounts don't have members.
Roles
| Role | May do |
|---|---|
| Admin | Change organization settings, change repository settings, and change other members' roles |
| Member | View repositories, reviews, and both settings pages; read-only |
Membership itself is decided by GitHub, not by EasyMerge: someone appears here once they have signed in to EasyMerge at least once and GitHub reports them as having access to the installation. There is no invite from this page, and no way to remove someone from it; that happens on GitHub.
Who becomes an admin
EasyMerge assigns admin by itself only while an organization has none, such as a fresh install. The GitHub account owner claims it the next time they sign in: an organization owner, or the account holder for a personal account. Installing the app does not grant it.
After that, everyone who signs in joins as a member, and the role dropdown is the only way to add another admin.
If EasyMerge cannot read organization membership (the Organization members: read permission is not yet accepted), the person who completed the install becomes admin instead.
An organization always keeps an admin: if the last one loses access on GitHub, the longest-standing member is promoted.
Changing a role
Admins pick Admin or Member from the dropdown on a member's row; it applies immediately. Members see roles as read-only badges.
- The installer is always an admin and has no dropdown.
- The last admin cannot be demoted. The change is refused with Failed to update member role. Promote a successor first.
Roles are per installation. You can be an admin of your personal installation and a member of your employer's.