Jump to content

Search the Community

Showing results for tags 'permissions'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Essentials
    • Announcements
  • Passwordstate 9.x
    • Community Support
    • General Hints and Tips
    • Known Issues
    • Installing Passwordstate
    • Feature Requests
    • Feature Requests - Completed
    • 3rd Party Hardware/Software Knowledge Forum
  • Knowledge Base
    • General FAQs
    • Password Resets
    • Remote Session Launcher
    • App Server
    • Passwordstate API
    • Browser Extensions
    • Password Reset Portal
  • Passwordstate 8.x
    • Community Support

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Jabber


Google Plus Account


Skype


AIM


Yahoo


ICQ


Website URL


MSN


Interests


Location


Biography


Location


Interests


Occupation

Found 6 results

  1. Please consider these two features: To make time based access easier to use, I'd like to set a default expiration time in the password list options, so that new permissions have time based access enabled unless it's explicitly disabled. To make the existing option "time based access mandatory" more effective, it should be possible to set a maximum expiration time. As an illustration of how I envision these options I made this rough mock-up:
  2. hi team, currently when searching for users in the Grant New Permissions dialog box, some users in the Search Results are blank. This is because it appears Passwordstate uses firstname+lastname to display the name. However, some of our accounts are service accounts to which we do not assign a first name and last name, only Display name. Is it possible for you to make the Display name in Passwordstate the same as the Display Name in Active Directory? that would much appreciated. Thank you
  3. We noticed the following behavior when searching for a user when granting permission on a folder, password list or inividiual secrets. When I enter the users first name I have no problem finding that user, it show a list of matching users with their first name and surname. When we search using the surname this is also show a list of matching users with their first name and surname. When I combine firstname and surname in the search field it does show any results. Could the search field be changed so it can combine search using firstname + surname? We haven over 20000 users synced to our environment and most of our users use firstname + surname when setting user permissions.
  4. Hello, I am wondering if there is a possibility to prevent users deleting passwords if they have Modify permissions. Or, if it's possible to have a fourth option for permissions where it allows them to add/change passwords, but not delete. Just trying to tighten up some control. Thanks!
  5. Please add an option to select multiple rows for deletion in the Permissions grid, for both password lists and folders. An option for "select all" would also be helpful. This could be similar to "Toggle visibility of delete checkboxes", which is one of the "List administrator actions" in a passwordlist. Currently, when removing many (or all) permissions for a passwordlist or a folder, I have to click twice per row that needs to be removed. When removing 20 or more permissions, this is quite a lot of work. The option "Administer Bulk Permissions for Password Lists" does not help, because it works per single user (or single security group), instead of for one passwordlist. And it does not work for folders. Thank you.
  6. Hi, We're a large IT group and we have multiple subsidiaries using a central passwordstate vault. Each subsidiary have it's own set of internal ou customers accounts / password / servers / ... We manage the segmentation on passwords using folders (advanced or standard permissions models) or lists: each team have its own root folder and manage their subfolders and lists inside. So people from team A cannot see passwords from team B unless they've been granted for. However, hosts are not manageable in the same way. No segmentation is possible for adding / deleting / editing hosts. So if someone from Team A add an host, people from Team B can remove this host. Each team needs to be fully autonomous for managing hosts, so we cannont centralize host insertion or edition to a central Team. We could like to have an host segmentation (per folder maybe ?) so if someone create an host in group / folder "A", only people that would have been admin rights grandted on that group can add / edit / remove it. Thanks.
×
×
  • Create New...