Freeze User who is logged in
If I freeze a user and if he is already logged into Salesforce, does he lose access? Or can he access it as long as he doesn't logout?
user-management
add a comment |
If I freeze a user and if he is already logged into Salesforce, does he lose access? Or can he access it as long as he doesn't logout?
user-management
you could just deactivate the user and then reactivate again, thus forcing a new SessionId and then freeze the user.
– akarnid
13 hours ago
This particular scenario is not documented clearly. I will think the best way to confirm this is to test it out.
– Jayant Das
13 hours ago
@akarnid the reason I didn't deactivated is because there are certain processes I need to follow before deactivating. So I freezed the user in the meantime. However, I don't want the user to access Salesforce while frozen.
– RajeshShah
13 hours ago
add a comment |
If I freeze a user and if he is already logged into Salesforce, does he lose access? Or can he access it as long as he doesn't logout?
user-management
If I freeze a user and if he is already logged into Salesforce, does he lose access? Or can he access it as long as he doesn't logout?
user-management
user-management
asked 14 hours ago
RajeshShahRajeshShah
1,1481229
1,1481229
you could just deactivate the user and then reactivate again, thus forcing a new SessionId and then freeze the user.
– akarnid
13 hours ago
This particular scenario is not documented clearly. I will think the best way to confirm this is to test it out.
– Jayant Das
13 hours ago
@akarnid the reason I didn't deactivated is because there are certain processes I need to follow before deactivating. So I freezed the user in the meantime. However, I don't want the user to access Salesforce while frozen.
– RajeshShah
13 hours ago
add a comment |
you could just deactivate the user and then reactivate again, thus forcing a new SessionId and then freeze the user.
– akarnid
13 hours ago
This particular scenario is not documented clearly. I will think the best way to confirm this is to test it out.
– Jayant Das
13 hours ago
@akarnid the reason I didn't deactivated is because there are certain processes I need to follow before deactivating. So I freezed the user in the meantime. However, I don't want the user to access Salesforce while frozen.
– RajeshShah
13 hours ago
you could just deactivate the user and then reactivate again, thus forcing a new SessionId and then freeze the user.
– akarnid
13 hours ago
you could just deactivate the user and then reactivate again, thus forcing a new SessionId and then freeze the user.
– akarnid
13 hours ago
This particular scenario is not documented clearly. I will think the best way to confirm this is to test it out.
– Jayant Das
13 hours ago
This particular scenario is not documented clearly. I will think the best way to confirm this is to test it out.
– Jayant Das
13 hours ago
@akarnid the reason I didn't deactivated is because there are certain processes I need to follow before deactivating. So I freezed the user in the meantime. However, I don't want the user to access Salesforce while frozen.
– RajeshShah
13 hours ago
@akarnid the reason I didn't deactivated is because there are certain processes I need to follow before deactivating. So I freezed the user in the meantime. However, I don't want the user to access Salesforce while frozen.
– RajeshShah
13 hours ago
add a comment |
2 Answers
2
active
oldest
votes
Based on a quick test in my DE Org, if an admin Freezes a User while the User is already logged in and accessing Salesforce, the User session is immediately terminated. The User cannot navigate to any other page/tab within the application once Frozen. The User is presented with a message as below.
Incorporating @sfdcfox's comment: The behavior is same if a User is deactivated.
Same behavior if you deactivate the user, too.
– sfdcfox
10 hours ago
Good to know, will add your feedback in the answer to make it more comprehensive.
– Jayant Das
10 hours ago
Thank you @JayantDas
– RajeshShah
36 mins ago
add a comment |
Salesforce checks the session's validity with every transaction. This means that if the user tries to continue working outside their Login Hours, while Frozen or deactivated, or if the IP address changes and "Lock session to IP address" changes, they will not be able to access Salesforce. There's no way to continue using a session if you're not allowed in the system for any security policy.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f250005%2ffreeze-user-who-is-logged-in%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Based on a quick test in my DE Org, if an admin Freezes a User while the User is already logged in and accessing Salesforce, the User session is immediately terminated. The User cannot navigate to any other page/tab within the application once Frozen. The User is presented with a message as below.
Incorporating @sfdcfox's comment: The behavior is same if a User is deactivated.
Same behavior if you deactivate the user, too.
– sfdcfox
10 hours ago
Good to know, will add your feedback in the answer to make it more comprehensive.
– Jayant Das
10 hours ago
Thank you @JayantDas
– RajeshShah
36 mins ago
add a comment |
Based on a quick test in my DE Org, if an admin Freezes a User while the User is already logged in and accessing Salesforce, the User session is immediately terminated. The User cannot navigate to any other page/tab within the application once Frozen. The User is presented with a message as below.
Incorporating @sfdcfox's comment: The behavior is same if a User is deactivated.
Same behavior if you deactivate the user, too.
– sfdcfox
10 hours ago
Good to know, will add your feedback in the answer to make it more comprehensive.
– Jayant Das
10 hours ago
Thank you @JayantDas
– RajeshShah
36 mins ago
add a comment |
Based on a quick test in my DE Org, if an admin Freezes a User while the User is already logged in and accessing Salesforce, the User session is immediately terminated. The User cannot navigate to any other page/tab within the application once Frozen. The User is presented with a message as below.
Incorporating @sfdcfox's comment: The behavior is same if a User is deactivated.
Based on a quick test in my DE Org, if an admin Freezes a User while the User is already logged in and accessing Salesforce, the User session is immediately terminated. The User cannot navigate to any other page/tab within the application once Frozen. The User is presented with a message as below.
Incorporating @sfdcfox's comment: The behavior is same if a User is deactivated.
edited 10 hours ago
answered 11 hours ago
Jayant DasJayant Das
14.1k2824
14.1k2824
Same behavior if you deactivate the user, too.
– sfdcfox
10 hours ago
Good to know, will add your feedback in the answer to make it more comprehensive.
– Jayant Das
10 hours ago
Thank you @JayantDas
– RajeshShah
36 mins ago
add a comment |
Same behavior if you deactivate the user, too.
– sfdcfox
10 hours ago
Good to know, will add your feedback in the answer to make it more comprehensive.
– Jayant Das
10 hours ago
Thank you @JayantDas
– RajeshShah
36 mins ago
Same behavior if you deactivate the user, too.
– sfdcfox
10 hours ago
Same behavior if you deactivate the user, too.
– sfdcfox
10 hours ago
Good to know, will add your feedback in the answer to make it more comprehensive.
– Jayant Das
10 hours ago
Good to know, will add your feedback in the answer to make it more comprehensive.
– Jayant Das
10 hours ago
Thank you @JayantDas
– RajeshShah
36 mins ago
Thank you @JayantDas
– RajeshShah
36 mins ago
add a comment |
Salesforce checks the session's validity with every transaction. This means that if the user tries to continue working outside their Login Hours, while Frozen or deactivated, or if the IP address changes and "Lock session to IP address" changes, they will not be able to access Salesforce. There's no way to continue using a session if you're not allowed in the system for any security policy.
add a comment |
Salesforce checks the session's validity with every transaction. This means that if the user tries to continue working outside their Login Hours, while Frozen or deactivated, or if the IP address changes and "Lock session to IP address" changes, they will not be able to access Salesforce. There's no way to continue using a session if you're not allowed in the system for any security policy.
add a comment |
Salesforce checks the session's validity with every transaction. This means that if the user tries to continue working outside their Login Hours, while Frozen or deactivated, or if the IP address changes and "Lock session to IP address" changes, they will not be able to access Salesforce. There's no way to continue using a session if you're not allowed in the system for any security policy.
Salesforce checks the session's validity with every transaction. This means that if the user tries to continue working outside their Login Hours, while Frozen or deactivated, or if the IP address changes and "Lock session to IP address" changes, they will not be able to access Salesforce. There's no way to continue using a session if you're not allowed in the system for any security policy.
answered 10 hours ago
sfdcfoxsfdcfox
255k11198438
255k11198438
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f250005%2ffreeze-user-who-is-logged-in%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
you could just deactivate the user and then reactivate again, thus forcing a new SessionId and then freeze the user.
– akarnid
13 hours ago
This particular scenario is not documented clearly. I will think the best way to confirm this is to test it out.
– Jayant Das
13 hours ago
@akarnid the reason I didn't deactivated is because there are certain processes I need to follow before deactivating. So I freezed the user in the meantime. However, I don't want the user to access Salesforce while frozen.
– RajeshShah
13 hours ago