Admin API?

[idselectronics]

Is there any official way to perform administrative tasks such as setting folder security without having to use the web admin page?

I'd like to be able to perform batch folder security operations. While there is a client API, I can find no evidence of an admin API anywhere.

[Beth]

There currently isn't a separate API for administrative tasks.

Are you changing folder security often, or do you just have a lot of folder security assignments to make?

You may find using Groups helpful. If you'd like some examples send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread.

[idselectronics]

There currently isn't a separate API for administrative tasks.

Are you changing folder security often, or do you just have a lot of folder security assignments to make?

You may find using Groups helpful. If you'd like some examples send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread.

We are potentially changing folder security often, yes. Essentially, we would like the ability for users to create new projects in the root and set their own permissions. In other words, ownership. We were hoping to expand upon the permission sets currently available by creating our own admin GUI that uses the admin account to perform security tasks based upon authentication against a separate database. As it stands, if you can create a project in the root, you can then see all other projects in the root and potentially "mess" with them by accident. We like to take the approach of no access by default.

I realize our methods are probably outside the norm, here. However, I would really appreciate it if an admin API would be put up for consideration with development.

Thank you!

[Beth]

What if you made a root folder for each user to create their projects there? Then each user would only have access to their root folder. Permissions inherit down through folders, therefore when they create new projects in their own root folders, other users won't see those projects.

[idselectronics]

What if you made a root folder for each user to create their projects there? Then each user would only have access to their root folder. Permissions inherit down through folders, therefore when they create new projects in their own root folders, other users won't see those projects.

Yes, I suppose this may simply require a change in attitude and structure on our part. I realize we are a tad unorthodox. However, even that suggestion would still not give the users control over adding permissions for other users to view their projects, would it? Again, the goal is to provide "ownership" over projects so that they can be administered independently.

[Beth]

I will still put in a feature request for an admin API.

F: 16454

Admin level rights happen at a repository level, not at a folder level. You could provide users admin level rights to a repository, and then they could assign rights to their folders, but they could set rights for all folders then.

Another option might be to give users their own repositories, as long as users don't need to merge change sets between each others' projects. Then they could be admins to their own repositories and manage the rights. You can make as many repositories as you'd like.

[Beth]

I did find some of our admin functions are available through our Vault CLC. You might be able to use that in helping some users manage other users. CLC documentation can be found here, http://download.sourcegear.com/misc/vau ... nt/clc.htm, and some examples are posted here, http://support.sourcegear.com/viewtopic ... 13&t=15235.