Application Administration
This section describes everything an organization administrator sets up in Q247, together with the technical specification for the teams that need to approve the deployment.
In the application this part is a single panel, Manage Organization, reachable from the top navigation and split into four tabs. In the documentation we have added three topics to them that do not have their own tab in the panel, but without which the picture would be incomplete: the permission model, the code-scanning component, and the security specification.
Parts of this section
Configuration is the panel's fourth tab: integrations with external systems and the rules Q247 uses to calculate and display data. Most of the deployment work happens here, which is why this part comes first in the documentation.
Manage organization covers the panel's first three tabs: accounts and teams, projects, and data sources. This is the day-to-day administrative work, done after deployment.
Permissions explains the access model that runs through all the other pages: organizational roles, access to a specific project, and team roles. Worth reading before granting anyone access, because these three layers work independently and it is easy to confuse their effects.
Enterprise Plugin is the component that actually clones repositories and calculates metrics from them. The Q247 panel only tells it what to scan. This part covers system requirements and installation.
Security is the specification for security and IT teams: algorithms, connection directions, and closed lists of the data passed along.
Subpages
Configuration
9 items
Manage Organization
3 items
Permissions
Three independent layers of permissions, organizational roles, project access, and team roles.
Enterprise Plugin
1 item
Security
3 items
Deployment path from scratch
If you are configuring Q247 for a new organization, the order is as follows:
- The plugin, in the Q247 cloud variant or installed locally, see Installation.
- A connector to the version control system, see Connectors.
- Assigning repositories to projects and activating people, see Starting code analysis.
- Jira and Confluence integrations, if the organization wants to measure workflow and documentation effort.
- Calculation rules: Flow Metrics boundaries, work calendar, exclusions.
- Accounts and access: manually or via SCIM, plus choosing a sign-in method.
The third step is the one most often skipped, and it is the one behind the situation where everything looks configured, yet the dashboards are empty.
Division of responsibility
| Scope | Who is needed |
|---|---|
| Q247 panel | an account with the Admin role in the organization |
| Tokens for repositories, Jira, Confluence | administrators of those systems |
| Installing the plugin in the Customer's infrastructure | the Customer's infrastructure team |
| Network rules and certificates | the Customer's network team |
| The Q247 app in the Atlassian site, plugin settings | the Q247 deployment team |