Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Improvement]: EMUs org membership types (drop-down) #15733

Closed
docs-bot opened this issue Feb 22, 2022 · 2 comments
Closed

[Improvement]: EMUs org membership types (drop-down) #15733

docs-bot opened this issue Feb 22, 2022 · 2 comments
Assignees
Labels
content This issue or pull request belongs to the Docs Content team MLH fellowship This issue is reserved for the MLH Fellowship program stale There is no recent activity on this issue or pull request

Comments

@docs-bot
Copy link
Collaborator

docs-bot commented Feb 22, 2022

This issue is reserved for MLH fellow program

What article(s) is affected?

Describe the desired docs changes

"Viewing people in your enterprise"

  • Add a new section after "Viewing dormant users" called "Filtering by member type"
  • Note callout that clarifies this is only available if your enterprise uses EMUs
  • Brief conceptual paragraph that explains why you'd want to use the Type filter (to see whether a person's membership is managed by an IdP group or they were manually added, so you know how to remove them)
  • Procedure for using the Type filter

"About Enterprise Managed Users"

  • In "About Enterprise Managed Users" section, after the paragraph that begins "Organization membership can be managed manually or updated automatically", mention that the way a person is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed, and that you can determine how a person was added using the Type filter, link to new section
@docs-bot docs-bot added the help wanted Anyone is welcome to open a pull request to fix this issue label Feb 22, 2022
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Feb 22, 2022
@ramyaparimi ramyaparimi removed the triage Do not begin working on this issue until triaged by the team label Feb 22, 2022
@janiceilene janiceilene added MLH fellowship This issue is reserved for the MLH Fellowship program content This issue or pull request belongs to the Docs Content team and removed help wanted Anyone is welcome to open a pull request to fix this issue labels Mar 17, 2022
@riteshsp2000 riteshsp2000 self-assigned this Apr 19, 2022
@janiceilene
Copy link
Contributor

@riteshsp2000 Are you still working on this one? If not, totally okay, we'll just move it back to the internal repo.

@github-actions
Copy link
Contributor

A stale label has been added to this issue becuase it has been open for 60 days with no activity. To keep this issue open, add a comment within 3 days.

@github-actions github-actions bot added the stale There is no recent activity on this issue or pull request label Jun 24, 2022
@github-project-automation github-project-automation bot moved this to Weeks 4-6 in MLH Fellowship Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team MLH fellowship This issue is reserved for the MLH Fellowship program stale There is no recent activity on this issue or pull request
Projects
Status: Weeks 4-6
Development

No branches or pull requests

4 participants