Customize/Limit Role Access within CommandMC
We would like the ability for the OP to customize/limit the access roles have to CommandMC applets. KWRI would set the standard access points for an assigned role, and the OP would have the ability to remove/limit access to specific applets that may not pertain to that role within their MC. Example, MC Leader role allows edit access to Recruits, Reports, Transactions, Accounting, and … The individuals with MC Leader role in this example MC do not need nor would the OP like for them have edit access to Transactions and Accounting, so the OP can remove access to Transactions and Accounting without removing their access to the Recruits and Reports applet. Additional instance, the OP could allow the MC Leader the ability to add MLS Ids or update recovery emails access. Currently, we are only able to remove a role to limit access, and there are many MCs that utilize the MC Leader role to support in growth activities. By implementing this request, it will allow for customized role access to support each individual office’s needs.
Kayla Garcia
shared this idea
-
LABS Team
commented
Allowing individual teams to access to only recruit information would allow transparency into the onboarding process and allow them access to the HeatSeeker list for their own recruiting purposes. Currently there is no way to safely provide an UpToDate HeatSeeker list to our teams without exporting the list weekly into a google sheet. This is ineffective as we cannot accurate keep notes on each possible recruit and capture all HeatSeeker leads.
-
LABS Team
commented
TO WHOM IT MAY CONCERN:
We need our ASC to have the ability to perform all related agent add/remove functions WITHOUT having access to sensitive CommandMC Compliance (red bubbles) info.
Recently an Angel advised us, "...if she (ASC) is just sending an Invitation to Join, then the MC Leader role would be sufficient, as this allows access to the recruits section of Command. However, there are certain tasks that require MCA/AMCA access, such as activating an associate.
Our Agents Services Coord (ASC) should be able to send new agent invites and activate new agents....all related agent add/remove functions WITHOUT having access to sensitive CommandMC Compliance (red bubbles) info.
Please understand we simply cannot have our ASC seeing sensitive info in CommandMC. This is simply not acceptable. If KWRI engineering cannot create a new Leadership Role to accommodate this seemingly basic task, then we will continue to be bogged down by this decision. This is not an efficient setup for our Market Center.
Bob Bethke, MCA - KW PARK CITY (MC#586)
-
LABS Team
commented
I have a couple of different virtual assistants out of the US that I'd like to delegate tasks to in Command MC for additional support (similar to how a single agent can have two assistants logging to Command). I'd love for both of them to be able to have their own login to Command MC so I can accurately assign tasks within the team. What I've previously been told is they can't be added because they don't have a social security number. Adding this feature would be a huge help to our MC operations.