This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Suggested feature requests / changes for SMC

Hi,

We've recently moved from a competitors product to Sophos Mobile Control, and thus far we're quite impressed. However after doing some usability testing the following valid points (in our opinion) have come up...

1. In order to make the URL easier to remember for the Self Service Portal it should be accessible without the /SSP, and instead the SMC Management portal should have something like an /Admin switch

E.g.

https://smc.domain.com = SSP page

https://smc.domain.com/admin = SMC Management portal

2. In order to avoid a user accidentally choosing the wrong device type the user should be forced to select either private or corporate. This is instead of the SSP defaulting to 'private'.

3. You should be able to set a different default SSP Task bundle for private and corporate devices

4. And the most annoying of all - the shear fact that the user must open and re-close the Sophos Control application before the application can be activated from the portal, and therefore check the device for compliance.

With all of these shortcomings we have chosen not to use the Self Service Portal. It’’’’s a nice idea but its usability is quite poor.

If anyone from Sophos product management want's to discuss these points then feel free to contact me.

Thanks,

John

:40499


This thread was automatically locked due to age.
Parents
  • HI John,

    to 6.)

    Maybe there is a big misunderstanding here. The SMC SSP users must come form one user group. But this does not mean, you have to give up the existing user groups. You can use them in the SSP to apply different profiles to them.

    The SSP user group just defines the users, which are allowed to log into the SSP. I recommend you create a new one with the name like SMC_SSP_Users and assign it to the respective users.

    If you define settings in the super admin customer, they will become available in all other customers

    to 7.)

    First of all, I assume, because of point 6, you do not really want to have different customers/tenants. If we resolve your point 6, the need for this will go away.

    We did not implement the pull down list for data privacy reasons. One customer can be defined by default and will be prefilled, but the rest must be entered

    Best regards

    Thomas

    :40611
Reply
  • HI John,

    to 6.)

    Maybe there is a big misunderstanding here. The SMC SSP users must come form one user group. But this does not mean, you have to give up the existing user groups. You can use them in the SSP to apply different profiles to them.

    The SSP user group just defines the users, which are allowed to log into the SSP. I recommend you create a new one with the name like SMC_SSP_Users and assign it to the respective users.

    If you define settings in the super admin customer, they will become available in all other customers

    to 7.)

    First of all, I assume, because of point 6, you do not really want to have different customers/tenants. If we resolve your point 6, the need for this will go away.

    We did not implement the pull down list for data privacy reasons. One customer can be defined by default and will be prefilled, but the rest must be entered

    Best regards

    Thomas

    :40611
Children
No Data