Skip to content
This repository was archived by the owner on Apr 7, 2025. It is now read-only.

Commit df2b234

Browse files
authored
Update People management UI (Cloud and CE) (#350)
* Update People management UI (Cloud and CE) * Autopromotion should use main
1 parent 4f4be57 commit df2b234

File tree

7 files changed

+61
-87
lines changed

7 files changed

+61
-87
lines changed

.semaphore/semaphore.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,4 +51,4 @@ promotions:
5151
pipeline_file: prod.yml
5252
deployment_target: Production
5353
auto_promote:
54-
when: "result = 'passed' and branch = 'master'"
54+
when: "result = 'passed' and branch = 'main'"
88.1 KB
Loading
175 KB
Loading

docs/docs/using-semaphore/organizations.md

Lines changed: 11 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -75,31 +75,24 @@ To manage users in your organization, open the organization menu and select **Pe
7575

7676
### How to invite users {#add-people}
7777

78-
To invite a user to your organization, press the **Add people** button. You have two options:
78+
To invite a user to your organization, press the **Add people** button:
7979

80-
- **By their [GitHub username](https://docs.github.com/en/get-started/learning-about-github/github-glossary#username)**, e.g. `TomFern`
80+
![People tab](./img/people-tab.jpg)
8181

82-
- Type their GitHub handle
83-
- Press **Invite**
84-
85-
![Adding users by their GitHub handle](./img/github-handle.jpg)
86-
87-
This option **does not allow email addresses** and doesn't send email notifications to users. To notify users via email, use the option below.
88-
89-
- **By existing projects**
90-
91-
The list shows GitHub and BitBucket users that already have access to repositories but have not yet been added to the Semaphore project
82+
<Steps>
9283

93-
- Select the users and optionally type an email
94-
- Press **Add selected** to add them to the organization and project
84+
1. Select one of the table: **Email**, **GitHub**, **BitBucket**, or **GitLab**
85+
- For email: type their email and optionally their username. A temporary password is shown. The user must change it on first login.
86+
- For other options: type their handle, e.g. `TomFern`
87+
- You may alternatively select users from the list. The list shows not-yet-invited users with access to at least one of the repositories
9588

96-
![Adding users to the organization](./img/add-people.jpg)
89+
![Invite users](./img/invite-user.jpg)
9790

98-
:::note In case of delays
91+
2. Press **invite**
92+
3. Optionally, set their [role](#roles-people)
9993

100-
In case of delays, click on the **Refresh** button in the top right corner of the page after sending an invite. This will trigger a sync between GitHub and Semaphore, which can typically last up to 2 to 5 minutes.
10194

102-
:::
95+
</Steps>
10396

10497
### How to remove users {#remove-users}
10598

docs/versioned_docs/version-CE/getting-started/features.md

Lines changed: 46 additions & 64 deletions
Original file line numberDiff line numberDiff line change
@@ -19,92 +19,74 @@ Legends: ? (unknown), p (pending/planned), x (deleted pages/content), c (confirm
1919

2020
| Feature | Semaphore Cloud | Semaphore CE |
2121
|--|--|--|
22-
| cVisual editor | Yes | Yes |
23-
| cArtifacts | Yes | Yes |
24-
| cTasks | Yes | Yes |
25-
| ?SSH Debug | Yes | Yes (but SSH debugging is not available for self-hosted jobs)|
26-
| cCache | Yes | Yes |
27-
| pMonorepo support | Yes | Yes (depends on initialization jobs) |
28-
| pInitialization jobs | Yes | Yes |
29-
| cSelf-hosted agents | Yes | Yes |
30-
| cGitHub support | Yes | Yes |
31-
| cBitBucket support | Yes | Yes |
32-
| cxPromotions | Yes | No |
33-
| cxParameterized promotions | Yes | No |
34-
| cxDeployment targets | Yes | No |
35-
| cxPre-flight checks | Yes | No |
36-
| cxsem-service & sem-versin | Yes | No |
22+
| Visual editor | Yes | Yes |
23+
| Artifacts | Yes | Yes |
24+
| Tasks | Yes | Yes |
25+
| SSH Debug | Yes | Yes |
26+
| Cache | Yes | Yes |
27+
| Monorepo support | Yes | Yes |
28+
| Initialization jobs | Yes | Yes |
29+
| Self-hosted agents | Yes | Yes |
30+
| GitHub support | Yes | Yes |
31+
| BitBucket support | Yes | Yes |
32+
| Promotions | Yes | No |
33+
| Parameterized promotions | Yes | No |
34+
| Deployment targets | Yes | No |
35+
| Pre-flight checks | Yes | No |
36+
| sem-service & sem-version | Yes | No |
3737

3838

3939
## Dashboards
4040

4141
| Feature | Semaphore Cloud | Semaphore CE |
4242
|--|--|--|
43-
| pTest reports | Yes | Yes |
44-
| cActivity monitor | Yes | Yes |
45-
| cxCustomeDashboards | Yes | No |
46-
| cxFlaky tests | Yes | No |
47-
| cxProject insights | Yes | No |
48-
| cxOrganization health | Yes | No |
43+
| Test reports | Yes | Yes |
44+
| Activity monitor | Yes | Yes |
45+
| CustomeDashboards | Yes | No |
46+
| Flaky tests | Yes | No |
47+
| Project insights | Yes | No |
48+
| Organization health | Yes | No |
4949

5050

5151
## Security and compliance
5252

5353
| Feature | Semaphore Cloud | Semaphore CE |
5454
|--|--|--|
55-
| cProject-level secrets | Yes | Yes |
56-
| cOrganization secrets | Yes | Yes |
57-
| cxPolicies for accessing secrets | Yes | No |
58-
| cxAudit logs | Yes | No |
55+
| Project-level secrets | Yes | Yes |
56+
| Organization secrets | Yes | Yes |
57+
| Policies for accessing secrets | Yes | No |
58+
| Audit logs | Yes | No |
5959

6060

6161
## User and permissions management
6262

63-
NOTE: see actual implementation to determine what needs to be deleted from organizations.md
64-
6563
| Feature | Semaphore Cloud | Semaphore CE |
6664
|--|--|--|
67-
| cMultiple organizations | Yes | No |
68-
| cInvite users to your organization | Yes | Yes |
69-
| cOrganization roles | Yes | Yes |
70-
| ?Project roles | Yes | Yes (*) |
71-
| cxUser groups | Yes | No |
72-
| cxCustom Roles | Yes | No |
65+
| Multiple organizations | Yes | No |
66+
| Invite users to your organization | Yes | Yes |
67+
| Organization roles | Yes | Yes |
68+
| Project roles | Yes | Yes (*) |
69+
| User groups | Yes | No |
70+
| xCustom Roles | Yes | No |
7371

7472
(*) Project roles exist but cannot be manually assigned to individual users. The role is assigned based on project-membership and org-wide user roles.
7573

7674
## Integrations
7775

78-
NOTE: what about Github SSO? affects Connect GitHub and Single Sign on GitHub pages
79-
8076
| Feature | Semaphore Cloud | Semaphore CE |
8177
|--|--|--|
82-
| cRepository status checks | Yes | Yes |
83-
| cRepository badges | Yes | Yes |
84-
| ?Slack notifications | Yes | Yes |
85-
| ?Webhook notifications | Yes | Yes |
86-
| cxSAML/SCIM integrations | Yes | No |
87-
| cxOkta integration | Yes | No |
88-
| cxOpenID Connect | Yes | No |
89-
| ?GitHub SSO | Yes | ? |
90-
91-
## Questions
92-
93-
Change/forgot password?
94-
Maintenance/upgrade Semaphore
95-
Take backups? Restore an installation?
96-
Renew/install certificates
97-
98-
Do project roles exist? or we just have to use org roles? They exist, but you cannot assign them, just view them. You can add/remove people from projects and that's it.
99-
TODO: is oauth still supported? I can't make it work
100-
101-
How do project permissions work? Do I need to invite user to my org with email and then manually add them to the project? Does it check for collaborators on the repo?
102-
How do I grant permissions to a user to a project? Do I need to give him admin on the org?
103-
Confirm with alek: Are there any plans to sem-service or sem-version to self-hosted agent jobs? NO
104-
105-
Are there any plans to add SSH debugging to self-hosted jobs?
106-
Will GitHub SSO be included in CE?
107-
108-
Should pull request trigger workflows?
109-
Do status badged work?
110-
How do I make the cache work on k8s? The docs only talk about VMs
78+
| Repository status checks | Yes | Yes |
79+
| Repository badges | Yes | Yes |
80+
| Slack notifications | Yes | Yes |
81+
| Webhook notifications | Yes | Yes |
82+
| SAML/SCIM integrations | Yes | No |
83+
| Okta integration | Yes | No |
84+
| OpenID Connect | Yes | No |
85+
| GitHub SSO | Yes | No |
86+
87+
## See also
88+
89+
- [Guided tour](./guided-tour)
90+
- [Migration guides](./migration/overview)
91+
- [Install Semaphore CE](./install)
92+
Loading

docs/versioned_docs/version-CE/using-semaphore/organizations.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,19 +37,18 @@ To manage users in your Semaphore instance, open the server menu and select **Pe
3737

3838
To invite a user to your instance, press the **Add people** button.
3939

40+
4041
<Steps>
4142

4243
1. Type the email of the person you wish to invite
4344
2. Optionally, set a username. If not provided, the username is inferred from the email
44-
3. Press **Add member**
45-
4. Press **Reveal** to show the temporary password assigned to the new member
45+
3. Press **Create Accounts**
46+
4. Take note of the temporary passwords. On first login, users are prompted to change their passwords
4647

4748
![Add user screen](./img/add-user.jpg)
4849

4950
</Steps>
5051

51-
TODO: will the user get an email? Does he need to change the password?
52-
5352
### How to remove users {#remove-users}
5453

5554
Users can only be removed from the instance when they don't own any projects. You must [transfer the ownership](./projects#owner-change) of all the user's projects before they can be removed from Semaphore.

0 commit comments

Comments
 (0)