Security groups are how access follows people. Give a group access to an app or a site once, and everyone you add to the group gets it. This guide adds a new joiner to an existing group in the Microsoft Entra admin center, step by step.
When someone leaves, the first thing to do with their account is stop it being used. Block sign-in does exactly that: nobody can sign in as the person, and their mailbox, files and data stay where they are. This guide blocks a leaver in the Microsoft 365 admin center, shows what he sees when he tries to sign in, and does the same with PowerShell.
I changed someone's job title in the Microsoft Entra admin center, got Successfully updated, and the Properties tab still showed the old title. The save had worked; the page hadn't caught up. Reloading the browser page fixed it.
When someone leaves, Microsoft's offboarding steps sign them out of everything and block their sign-in. I blocked first, and the Microsoft 365 admin center then stopped offering Sign out of all sessions. Microsoft Entra's Revoke sessions still worked.
This part lets managers keep each job title's plan up to date: add a competency, change its level or remove it, from one Competency screen. Every change applies to everyone with that job title, so the screen says so, checks for duplicates, asks before removing, and tells reviewers when a plan changed under a response.
Adding an item and editing one need almost the same screen. Instead of building two, build one and open it in two ways: with the item's ID to edit it, or with a blank ID to add a new one. Each formula that differs asks one question, IsBlank(locCompetencyId).
Some actions deserve a second thought, such as removing something many people use. Instead of acting at once, the button asks a question on the same screen, with Yes and Cancel below it. Nothing happens until Yes, and screen readers announce the question.
A screen reader reads where the user is. When an action makes a message appear somewhere else, its users don't hear about it. A live region fixes that: screen readers announce whenever its text changes. In Power Apps, a classic Label becomes a live region with its Live property.
A soft delete hides an item instead of deleting it. A Yes/No column, such as IsActive, says whether the item is in use. "Removing" sets it to No, and every list in the app shows only items where it's Yes. The item stays in SharePoint with its history, and it can come back.
To stop people from adding the same item twice, look for it before you save. If a matching item exists, show a message and don't save. On SharePoint, the lookup can run in the list itself, as long as it compares columns with =.
