+1 703.350.4150 Have TeamExpand Call You Leave a Message

"I really like the way you can access your work items from within Outlook. I like the way you can bring up the full work item forms, make edits, and save immediately to TFS. It was great to create new meeting requests or mail messages from the work items."

Lori Lamkin
Product Unit Manager for Team Foundation Server at Microsoft

"These types of products are important to the industry."

Joel Semeniuk
CEO and co-founder of ImagiNET Resources Corp.

"I know of a good number of companies that will love having something like this - getting their timesheet management into TFS (so it can be reported on, especially) will make life a lot easier for them."

James Manning
Software Design Engineer for Visual Studio project at Microsoft

"I like the idea of being able to link work items to e-mails and meetings. I also like that it provides non-technical information workers the option of working with TFS in a more familiar environment. Congratulations to TeamExpand on the release!"

Jason Barile
Principal Test Manager for Visual Studio Team Foundation Server at Microsoft

"TX Chrono, by TeamExpand, allows users to easily track how they are spending their time, store that information in TFS, and make it available for reporting in the warehouse."

Brian Harry
Product Unit Manager for Team Foundation Server at Microsoft

Left 1 2 3 4 5 Right
TFS Timesheet

VSTS-Outlook Bridge

Blog

TFS Permissions

July 29th, 2008
by Alena Semeshko

Eugene Zakhareyev writes on TFS permissions and lists some principles to keep in mind when working with permissions. Here’s his list of best practices when it comes to working with the most problematic permissions area, version control specific permission issues :

1. Set as few permissions as possible. Ideally, you would set permissions on server, project and immediate project subfolders at most (and set server/project permissions by assignment to appropriate pre-defined groups). That way you will be able to immediately know where to look for the “root” of any permission problem.
2. Never set permission on files (that can be viewed as more of the same topic as in previous paragraph, but I cannot say that enough).
3. Use inheritance as much as possible; start with most permissive set-up and partition by using Deny.
4. If you find yourself setting certain permissions more than once, script them using tf permissions (use tfssecurity for global and area permissions). In this way potential for human error is minimized.

Add your own comment...

Post Comment





RSS entries or comments