How can we improve the SMA (K1000)?

K1000 Version 6 User Console Welcome Screen Logo

I think it would be a good idea to add a separate logo upload just for the welcome screen. The default user console logo is 224x50 and the default welcome screen logo is 311x160. In the current design, the user console logo is used for both. If you design your logo for one specific size, it may not look as good on in the other size. Also, you are dealing with two different color backgrounds.

When I use a larger logo(311x160) for the user console it is shrunk to fit the 224x50 requirements and is distorted. I am not sure about anyone else, but I am having issues with my user console logo showing up on my welcome screen as well. I attached a screen shots of my user console and welcome screens

31 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Matt L shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
under review  ·  Nick Buonpastore responded  · 

This is under consideration but not planned for the next release. Please continue voting if you’d like to see this feature prioritized for a future release

3 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • Shelly commented  ·   ·  Flag as inappropriate

    Just one more addition... I'd like the logo to also be displayed in the admin console. Sometimes I don't even know there are logo issues until a user reports them because I never use the user portal.

  • Shelly commented  ·   ·  Flag as inappropriate

    I have been struggling with this issue too. My logo looks horrible on the welcome screen but looks great on the user console screen. I can't find a happy medium with my logo colors unfortunately. Would really like to see this fixed. And in fact, I would like to have better customization options for the welcome page in general.

  • Anonymous commented  ·   ·  Flag as inappropriate

    I encountered this issue as well... The crazy thing is that I encountered different behaviors with different browsers. Testing with IE, Chrome and Firefox, it would work some some but not others and not consistently.
    Kace support called it a bug and gave me a number "bug # K1-16570"

Feedback and Knowledge Base