In order to deploy V1 across the enterprise, the product needs the flexibility and security features to support multi-tenancy. Simply put this requirement means that any configuration or customization that a tenant would want should not impact others tenants. Re-usable configuration schemes would still be valuable, so that multiple tenants could share configuration when desired.

by: Andres M. | over a year ago | Administration

Comments

• Yes, we have different teams whose projects need different custom fields for example.

  by: Kathy A. | over a year ago

• We also have the need to configure many items on a per project basis.

  by: Mike C. | over a year ago

• Yes. This is a good broad requirement that encompasses these that are more specific:
  
  https://ideaspace.versionone.com/default/Idea/Detail/234
  
  https://ideaspace.versionone.com/default/Idea/Detail/119

  by: Andrew F. | over a year ago

• We're taking a look at this in terms of where the flexibility can provide the most value (i.e. what things are different teams or organizations most likely to want to be different) as an option to fully segregated environments. We're happy to hear additional thoughts on the areas where you think your groups would choose to differentiate. Kathy provides an example above. Some other ideas also offer examples. Where would you have differences?

  by: Mark Crowe | over a year ago

  official response

• Looking at this and the two other similar items, I think the biggest item of interest would be the ability to customize fields on a per project basis. I think the project hierarchy could be quite useful in this case, with each project inheriting it's field configuration from its parent projects.
  
  For administering this, I think it would work initially to let a few instance admins manage this. However, in the long term, I think it would be best to allow project level administration privileges for the fields, as this would reduce administrative overhead for the projects as they fine tune they're configuration for themselves.

  by: Bryan D. | over a year ago

• We definitely need this, since if i want to customize the fields, I am afraid it will mess up the process of other teams.
  Also, when i start a new team or a new group, I'd like to use my old feature set as a template for that, or allow another team to use my configuration.

  by: Christopher S. | over a year ago

• Project Workspaces are available in the Summer '10 release.
  
  See the Release Notes: http://community.versionone.com/Release%20Notes/ReleaseNotes2010Summer.aspx

  by: Mark Crowe | over a year ago

  official response