# Unable to Assign a new Scoutmaster

**URL:** <https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862>\
**Category:** My Scouting Tools\
**Created:** [June 1, 2026, 6:30pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862 "2026-06-01T18:30:53Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![MichaelBenaitis](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@MichaelBenaitis](https://discussions.scouting.org/u/MichaelBenaitis)\
**Post date:** [June 1, 2026, 6:30pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862/1 "2026-06-01T18:30:53Z")

</div>

_1) Hardware: Desktop or Mobile (if mobile, please be specific)_

Desktop - Mac Chrome Flex OS - Chrome Browser

Desktop - HP Windows OS - Chrome Browser

Mobile - iPhone - Chrome browser

_2) Operating system  
3) Browser  
4) Browser cache has been cleared or you are using a private browsing mode (aka Incognito Window in Chrome)_

Cache has been cleared. Also tried using Incognito Mode.

- 

1. Member ID & Council of person affected  
Thank you!)\*

SM #12486882 Rainbow Council

ASM #128030740 Rainbow Council

I am attempting to switch the current SM to ASM and the ASM to SM. My.Scouting - Organization Manager - Position Manager, gives me an error message “System Error”. I also tried to make the change in SB+ - Permissions Manager - Assign Position. The delete button next to the SM’s name is grey and I am unable to select it. The drop down box to assign someone does not open. Hovering over both of them my cursor changes to a red do not enter symbol. I have a second Troop. My.Scouting and SB+ permit me to make changes to the SM and all other positions (except EO, I understand that the EO requires an application.)

Thank you,

---

<div class="post-metadata">

**Author:** ![DonovanMcNeil](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/donovanmcneil/32/24_2.png) [@DonovanMcNeil](https://discussions.scouting.org/u/DonovanMcNeil)\
**Post date:** [June 1, 2026, 6:36pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862/2 "2026-06-01T18:36:21Z")

</div>

First I would advise to talk to council.

What order are you trying to do it in? Adding ASM to SM position first?

---

<div class="post-metadata">

**Author:** ![MichaelBenaitis](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@MichaelBenaitis](https://discussions.scouting.org/u/MichaelBenaitis)\
**Post date:** [June 1, 2026, 6:43pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862/3 "2026-06-01T18:43:56Z")

</div>

I tried both ways. When I remove the SM first I get a message “A minimum of 1 person(s) must be assigned to this position.” But it goes away as soon as I put the ASM in the position.

When I move the ASM to SM first I get a message “Too many people are assigned to this position.” It goes away after I remove the previous SM.

I both cases I get a green box next to their names, seemingly indicating that it is an acceptable move. When I click save is when I get the “System Error” message.

---

<div class="post-metadata">

**Author:** ![MichaelBenaitis](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@MichaelBenaitis](https://discussions.scouting.org/u/MichaelBenaitis)\
**Post date:** [June 1, 2026, 6:44pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862/4 "2026-06-01T18:44:22Z")

</div>

Thanks, I will reach out to Council.

---

<div class="post-metadata">

**Author:** ![DonovanMcNeil](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/donovanmcneil/32/24_2.png) [@DonovanMcNeil](https://discussions.scouting.org/u/DonovanMcNeil)\
**Post date:** [June 1, 2026, 6:46pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862/5 "2026-06-01T18:46:00Z")

</div>

can you not do both before you save? I think that is how I did it in the past

---

<div class="post-metadata">

**Author:** ![MichaelBenaitis](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@MichaelBenaitis](https://discussions.scouting.org/u/MichaelBenaitis)\
**Post date:** [June 1, 2026, 6:57pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862/6 "2026-06-01T18:57:26Z")

</div>

I did both before I saved.

Now this is really weird. I just did the opposite and only moved one and then hit save.

Now both of them are SMs and ASMs. Both names under SM and both names under ASM.

I then get this pop up message " **This member is already assigned to two registered positions in this unit. Unassign one of the positions before assigning them to another position."** No matter what I do I keep getting that pop up. I don’t see an option to unassign. Just click and drag which gives me the pop up message.

And under the SM field “Too many people are assigned to this position.” but when I move them I get the pop up message again.

I’m going to log out and clear the cache again.

---

<div class="post-metadata">

**Author:** ![MichaelBenaitis](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@MichaelBenaitis](https://discussions.scouting.org/u/MichaelBenaitis)\
**Post date:** [June 1, 2026, 7:18pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862/7 "2026-06-01T19:18:16Z")

</div>

It still lists them both under SM and ASM. Now, My.Scouting will not let me change any positions seemingly until I remove one of them from SM.

There is not a delete button beside any names or positions under “Registered Positions” tab to select. In the “Functional Roles” tab I have the option to delete from a position.

Can I send you screen shots?

---

<div class="post-metadata">

**Author:** ![MichaelBenaitis](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@MichaelBenaitis](https://discussions.scouting.org/u/MichaelBenaitis)\
**Post date:** [June 3, 2026, 5:08pm UTC](https://discussions.scouting.org/t/unable-to-assign-a-new-scoutmaster/510862/8 "2026-06-03T17:08:05Z")

</div>

It is displaying correctly now.

Thank you
