Team functionality

[Jens Doose]

It would be nice if there would be more team support than just the "collaborator".

"collaborator" is nice for open-source projects etc., but it does not fit my needs when working with VersionEye in a business environment.

Main issue:

• The API needs a private API key as identification. This key is mapped to a specific user. In a team environment i would prefer a "Team API key", so my personal and private API key is not revealed when API calls are used in a CI environment (jenkins, etc.)

• Invite colleagues. They could be automatically on my "team" so I can add them as collaborators easily

• more ideas are on the way. We could do a brain storming while having a pizza :D @MaChristmann could join us ;)

[Robert Reiz]

@jdoose @MaChristmann I see the point. Your idea makes a lot of sense. I'm very open for Pizza and brain storming next week :-)

[Robert Reiz]

@jdoose @MaChristmann Here we go: http://blog.versioneye.com/2015/11/29/organisations-teams/

[Jens Doose]

Great work! Thanks!

[Tobias Preuss]

@reiz I created a organization here but as soon as I click on the link I end up at a "The page you were looking for doesn't exist." page.

[Robert Reiz]

@tbsprs That's because of the points in the name. Please create a another organisation without points and white spaces in the name. I will double check the JavaScript validation for that.

[Robert Reiz]

I just added a JavaScript validator. It goes online with the next deployment.

[Tobias Preuss]

Nice. I created a new organization. Is there a way to delete the old one?

[Robert Reiz]

@tbsprs I just removed it for you.

[Tobias Preuss]

Thank you.

[Robert Reiz]

@tbsprs Just added the JavaScript validator. It's deployed on production to prevent further mistakes!

[Tobias Preuss]

:+1: