Wissenszentrum
Wissenszentrum Home
BeeTagg User, Team, Credits and Permissions
Introduction

The BeeTagg System has been designed for the enterprise market where co-workers work together in teams and where co-workers have different responsibilities.

The BeeTagg System implements a structure that matches the setup of a typical company.

 

Core Concepts:
  • Codes belong to teams, not users.
  • Teams consist of one or many users.
  • Different users of a team can have different permissions.
  • BeeTagg Credits belong to a team, not a user.


The following figure illustrates a typical workflow:

 
Overview

Example of a typical user, team and permission setup:

  Team A Team B Team C
User 1 Permissions 1A Permissions 1B  
User 2   Permissions 2B Permissions 2C
User 3 Permissions 3A Permissions 3B Permissions 3C

For example, User 1 is member of Team A and Team B. His permissions for Team A and Team B can be different. Each of these terms are explained in the following sections.

 

BeeTagg User

A BeeTagg User is a single person who has access to the BeeTagg System. What he is able to do depends on his set of permissions. A user is identified by his username and password. To manage BeeTagg Codes a user must be singed in to the BeeTagg portal. 

 

BeeTagg Team

A team consists of one or many users and has the following properties:

  • BeeTagg Credits: Users buy and spend credits but always for a selected team.
  • Codes: These are always associated with exactly one team.
  • Team contacts
    • Technical contact
    • Billing contact
    • Owner contact

Different users of the same team can have different permissions. 
 

Permissions

A user can have different permissions for each team that he is a member. Therefore, a user needs to select a team before engaging in any team related actions. Permissions are split into two categories: basic and advanced permissions.

 

Basic permissions
  • User can add or edit codes (Modify Codes Permission)
  • User can read codes (Read Codes Permission)
  • User can modify this team (Modify Team Permission)
     
Advanced permissions
  • User can edit the Modify Codes Permission
  • User can edit the Read Codes Permission
  • User can edit the Modify Team Permission
  • Master Permission

 

Examples
 
Small company (1 user and 1 team)
 
The AwsomeMedia agency has three employees. Alice is managing the BeeTagg Service She has created an account and a BeeTagg Team - the AwsomeMedia team. After the setup she no longer needs to worry about the BeeTagg Team. Since she’s only in one team, that team is set as default for all her actions.

The company creates a handful of codes every month. All of them are under the same BeeTagg Team.
 

Large company (10 users and 1 team)
 
A company with 1500 employees uses the BeeTagg system in several departments: marketing to advertise products in media, product documentation to organize and link related online and paper documents and accounting to buy BeeTagg Credits for all departments.

The print shop also needs access for printing the codes on various documents (but isn't allowed to edit or create codes)

Therefore, the company creates two BeeTagg Teams:

  • TheCompany - Marketing campaigns
    All codes from the marketing team are created and managed under this team. Each marketing manager has its own BeeTagg user to create new codes and track statistics. The assistant of the Marketing vice-president is the owner of the BeeTagg Team and is responsible to manage the users in it..
  • TheCompany – Product documentation
    The documentation leads for the different products can create and update the codes using this team. All technical writers can read the codes in this team so they may, for example, generate them in the appropriate format in manuals or on the web site.

Sam works in the accounting department and is member of both BeeTagg Teams. For approved BeeTagg Credits requests he logs into the BeeTagg Portal and buys the requested amount of BeeTagg Credits for each team.

©2005-2018 connvision AG - Datenschutzerkl√§rung - Nutzungsbedingungen - Kontakt
German - English - DutchDutch is currently in Beta. Help us to improve! - RussianRussian is currently in Beta. Help us to improve! - TurkishTurkish is currently in Beta. Help us to improve!