Session status

Task completed. Sam clarified that the main goal was not to make this a conflict with Nathaniel or to over-focus on visibility; the real goal was to make sure people cannot use deprecated SMS Magic to send messages.

Positioning

This was handled as a functionality-safety cleanup, not as a person-specific correction. The earlier Lightning page visibility removal remains reversible. The more important follow-up was the permission layer.

Live findings

The SMS Magic package is still installed as SMS-Magic Converse, namespace smagicinteract, version 1.68.41.

Before the permission change, live ObjectPermissions showed broad Litify permission-set groups granting Create/Edit/Delete access on SMS Magic send-relevant objects:

• Litify_Standard_User_PSG
• Litify_Power_User_PSG

Those groups included SMS Magic permission sets, including:

• SMS_Magic_Custom_Permission_Set
• smagicinteract__SMS_Interact_Conversation_User
• smagicinteract__SMS_Interact_Permission_Set
• Power group also included smagicinteract__SMS_Converse_Custom_Metadata, smagicinteract__SMS_Converse_Custom_Setting, and smagicinteract__SMS_Interact_Template_Author.

Litify_Standard_User_PSG also included SMS_Drips_User.

What changed

A reversible metadata deploy removed the SMS Magic and SMS Drips permission sets from the broad Litify Standard and Power permission-set groups. This was not targeted at any individual user.

Removed from Litify_Standard_User_PSG:

• SMS_Drips_User
• SMS_Magic_Custom_Permission_Set