Solved How to logout of the 3CX Windows Application / Switch to a different account?

[Alan9846]

Hi All,

How do we logout of the 3CX Windows Application so that we can switch to a different account?

I am currently 'stuck' as a one given user of one single instance of 3CX in the Windows Application.

I haven't been able to find an option to logout. I can open multiple instances of the web interface for any number of different accounts (simultaneously if I want), but I can't seem to change at all in the Windows Application.

I believe it is likely to be the V18 Windows Application, but I cannot see any 'Help - About' type option to determine for certain.

Sorry for posting such a dummy question!

Alan.

 

[NickD_3CX]

Hi!

If you are referring to the new Desktop App, then this is focused more on single-account usage, so there is no way to quickly switch between various accounts.

You need to have this ability, then your best option is to continue doing what you said, opening multiple Webclient tabs each with different accounts.

 

[Alan9846]

Hi!

If you are referring to the new Desktop App, then this is focused more on single-account usage, so there is not way to quickly switch between various accounts.

You need to have this ability, then your best option is to continue doing what you said, opening multiple Webclient tabs each with different accounts.

Hi Nick,

Yes - this is the application installed on Windows, rather than the WebClient accessed via a browser.

How is it supposed to work where we have users sharing a computer? They are both using the same Windows login, but they each have their own extension number, so we need to be able to switch between the two.

They have been operating this way for a couple of years, so this must have been be possible until recently?

Also, for us as providers - I am often logging in to the Windows App as a client user to check things. Does that mean that I am forever locked to being that one user on one 3CX instance, and I can never login the Windows Application to any other client 3CX?

Thanks,

Alan.

 

[SteveITS]

If they use the web client they can just log out/in.
The legacy Windows client has the option in Settings/Configure Accounts to change accounts. This can still be used.
Can they just log in to Windows as a different Windows user? Then they have their own Desktop App install.

 

[Alan9846]

If they use the web client they can just log out/in.
The legacy Windows client has the option in Settings/Configure Accounts to change accounts. This can still be used.
Can they just log in to Windows as a different Windows user? Then they have their own Desktop App install.

Hi Steve,

No problem with the WebClient - this is with the Windows Application.

If I click into Settings, where do I find 'Configure Accounts'?






Thanks,

Alan.

 

[SteveITS]

That's the new Desktop App not the "v16" Windows Client. I know, the naming is a bit confusing. This:

 

[Alan9846]

Hi Steve,

I didn't know that the old v16 Windows Application was still active, but I am talking about the one I sent a screen shot of above (v18). I have migrated all of our clients to v18 already.

How do I switch to a different user / instance of 3CX in the v18 Windows Application?


Thanks,

Alan.

 

[SteveITS]

In the new Desktop App I think the way is to log in to the web client and reprovision the Desktop App so it is told what extension to use. (click Apps in the lower left corner of the web client) Then have each person do that when they sit down.

 

[Alan9846]

In the new Desktop App I think the way is to log in to the web client and reprovision the Desktop App so it is told what extension to use. (click Apps in the lower left corner of the web client) Then have each person do that when they sit down.

Hi Steve,

That worked - from the WebClient, I clicked on Apps, then 'provisioned' the Windows Application to that user.

Seems very cumbersome - a pretty major design flaw in the V18 Windows Application, but I guess we just have to tell clients to work around it until someone fixes it (if they ever do).


Thanks for sticking with me!

Alan.

 

[SteveITS]

If they log in to the web client, they can just use that and not worry about the Desktop App at all...

 

[Alan9846]

If they log in to the web client, they can just use that and not worry about the Desktop App at all...

That would be an argument for ditching the Windows Application altogether, but if there is to be a Windows Application then it should have been re-designed with a modicum more thought.

The problem is, I guess, that there is no way that a webpage will ever be as easy to access as an installed application, and if their browser is on a 'go slow' due to some crappy website slowing it down (Chrome at least - doesn't seem to happen with Edge or FireFox very often), then their telephony is also stuffed.

However, I don't try to tell clients what they should use - I just give them the options, and when they complain like above, I can only say that it is inherent to 3CX and they can choose a different phone system if they don't like it.



Alan.

 

[NickD_3CX]

That would be an argument for ditching the Windows Application altogether, but if there is to be a Windows Application then it should have been re-designed with a modicum more thought.

The problem is, I guess, that there is no way that a webpage will ever be as easy to access as an installed application, and if their browser is on a 'go slow' due to some crappy website slowing it down (Chrome at least - doesn't seem to happen with Edge or FireFox very often), then their telephony is also stuffed.

However, I don't try to tell clients what they should use - I just give them the options, and when they complain like above, I can only say that it is inherent to 3CX and they can choose a different phone system if they don't like it.



Alan.

Then may I suggest you make separate Windows Users for them. Each time someone finishes their shift or need to hand off to someone else, they log out, next person logs in.

In this scenario, each Windows User could have their own Desktop app config.

 

[Alan9846]

Then may I suggest you make separate Windows Users for them. Each time someone finishes their shift or need to hand off to someone else, they log out, next person logs in.

In this scenario, each Windows User could have their own Desktop app config.

Hi Nick,

If it were up to me, that would already be the case, but the client chooses not to operate like that (they don't even have a Windows Domain).

They don't have an issue with most (maybe any other) applications since most applications where identity is integral have the capability to sign in and sign out (a fairly basic security feature in any case) - unfortunately the 3CX Windows Application does not have that capability.

I have advised the client that 3CX does not have that option, and they have to go through the web interface, and re-provision the application each time the user changes. Not a pleasant user experience, but not really my problem.

If they complain too much, it looks like I can 'upgrade' them for Version 18 back to Version 16.

Thanks,

Alan.

 

[NickD_3CX]

Hi Nick,

If it were up to me, that would already be the case, but the client chooses not to operate like that (they don't even have a Windows Domain).

They don't have an issue with most (maybe any other) applications since most applications where identity is integral have the capability to sign in and sign out (a fairly basic security feature in any case) - unfortunately the 3CX Windows Application does not have that capability.

I have advised the client that 3CX does not have that option, and they have to go through the web interface, and re-provision the application each time the user changes. Not a pleasant user experience, but not really my problem.

If they complain too much, it looks like I can 'upgrade' them for Version 18 back to Version 16.

Thanks,

Alan.

"Upgrading" them from V18 to V16 is not a solution you want to go for because V16 is saying goodbye to use this year:
https://www.3cx.com/blog/news/v16-web-meeting-eol/

You could try Local Windows users, I believe that should do the trick too, so no Domain Controller required.

An alternative, although not ideal, but effective, is creating a BAT file for each user that does what is explained here:
https://www.3cx.com/community/threa...-3cx-desktop-app-v-18-7-10.87076/#post-411525

 

[Alan9846]

"Upgrading" them from V18 to V16 is not a solution you want to go for because V16 is saying goodbye to use this year:
https://www.3cx.com/blog/news/v16-web-meeting-eol/

You could try Local Windows users, I believe that should do the trick too, so no Domain Controller required.

An alternative, although not ideal, but effective, is creating a BAT file for each user that does what is explained here:
https://www.3cx.com/community/threa...-3cx-desktop-app-v-18-7-10.87076/#post-411525

Trouble is, it is not my network / machines - I am just the phone guy for this client.

As I said above, I think the best option is just to tell them that they have to live with the lost functionality, and if they don't like it, they can change to a different phone system.

I very much doubt that 3CX will be fixing it - they made a decision, and even though it is a poor one, they'll likely dig their heels in and refuse to change / fix it.

I'll move them back to V16 until that version of the Windows Application dies, and if that is prior to their license renewing (might be Aug 2022 - I can't recall) then they might have to lose a few months by transferring to a different phone system.

To be fair, it doesn't really matter to me either way as long as I stop them whinging at me

Thanks for the suggestions - I do appreciate it.

Alan.

 

[NickD_3CX]

You have 3 alternatives in this thread to choose from if you or the customer change your mind.

I will set this as 'Solved'.