All About SharePoint SharePoint 2010 and MOSS 2007 Resource Website

3Mar/111

Accessing the term store as a manager or contributor

Accessing the term store as a manager or contributor

Today 03/03, we ran into a situation where one of the users who manage the SharePoint 2010 Site was unable to access the term store management links.

I've touched on the term store a few times in posts this year. But as ever the best way to learn a new tool is to get a bit of practical experience. So I came across this little nugget this week when onsite with a client. Firstly a bit of background on the term store.
The building blocks of the term store are:

  • Metadata application: Top level container of our term store. Contains groups
  • Groups: Term sets are collected together in groups
  • Term set: A hierarchical group of related terms
  • Term: The basic building block of the term store. A metadata word

The term store can be managed by the following three groups of people:

  • Term store administrator: Full control over the term store, and able to assign other people roles.
  • Group managers: This role allows a user to manage a particular group of term sets
  • Contributers: This role allows users to manage terms sets in a particular group, but they are not able to create additional contributers.

Term sets also have 'owner' and 'stakeholders' properties but these aren't actually used for anything.

Anyway the reason for this was post was to talk about how the roles described above access the term store. If the user has sufficient permissions to see 'site settings in 'site actions' then there isn't really an issue. They can navigate to site settings, and into the term store. However if the user cannot see the 'site actions' button their is no easy way to navigate to the term store at all. In fact it seems the only way is to link directly to it (and make sure you link to the term stored access via 'site setting's not central administration) and either distribute the link or post it somewhere. Whilst we have always had different permissions models outside of the standard user access model, this feels a bit different and all a bit unfinished. Have a look and see what you think. Comments below please.