Sider Documentation

Sider Documentation

›Getting Started

Getting Started

  • Home
  • Intro Videos
  • Setting up Sider
  • Dashboard Overview
  • Repository Settings
  • Custom Analysis Configuration
  • Working with Issues
  • Permissions
  • Skip Analyzing

Analysis Tools

    Ruby

    • RuboCop
    • Reek
    • Querly
    • Rails Best Practices
    • Brakeman
    • HAML-Lint

    Java

    • Checkstyle
    • PMD
    • JavaSee

    Kotlin

    • ktlint

    JavaScript and Flavors

    • ESLint
    • JSHint
    • TSLint
    • TyScan
    • CoffeeLint

    CSS

    • stylelint
    • SCSS-Lint

    PHP

    • Phinder
    • PHPMD
    • PHP_CodeSniffer

    Python

    • Flake8

    Swift

    • SwiftLint

    Go

    • go vet
    • Golint
    • Go Meta Linter

    C/C++

    • Cppcheck
    • cpplint

    Shell script

    • ShellCheck

    Others

    • Goodcheck
    • Misspell

Custom Rules

  • Intro to Custom Rules
  • Goodcheck
  • Tips & Tricks

Advanced Settings

  • Inline Comments
  • Private Dependencies
  • Restricting access to Close button
  • Transferring a repository

Billing and Plans

  • Billing and Plans

Troubleshooting

  • Troubleshooting

Enterprise

  • Outline
  • Quickstart
  • Computer Resources
  • GitHub Setup
  • Database Guide
  • Object Storage Guide
  • Containers Guide
  • Updating Guide
  • Administration Guide
  • Scaling Guide
  • Configuration Index
  • Health Check Guide
  • Releases

    • Summary
    • 201911
    • Older releases

News

  • 2019
Edit

Permissions

Users are required to have specific permissions to perform certain actions with Sider. Because Sider is integrated into GitHub, names of permission levels are the same as those set on GitHub. If you need more information about permission levels, read the GitHub documentations: "Permission levels for an organization" and "Repository permission levels for an organization".

For the organization settings, Sider checks for permissions in an organization. For the repository settings, appropriate permissions to a repository is needed.

Permissions requirement for an organization

ActionBilling ManagerMembersOwners
Install SiderX
See repository adding pageXX
Add repositoriesX¹X
See repositoriesX²X
Enable repositoriesX
Delete repositoriesX
Register credit cardsX
Upgrade planX
Cancel planX
Assign seatsX
Sync with GitHubX
Invite membersX
Add Billing ManagerX
Edit Billing ManagerX
Delete Billing ManagerX
Show invoicesXXX
Add supplementary information to a invoiceX

¹ Admin permission to a repository is required.

² Only repositories you can access will be displayed.

Permissions requirement for a repository

ActionRead permissionsWrite permissionsAdmin permissions
Add repositoriesX³
See analyzing/analyzed pull requestsXXX
See analysis resultsXXX
Comment to issuesXXX
Comment and close issuesX⁴X
Close issuesX⁴X
Close all issues simultaneouslyX⁴X
Reopen issuesX⁴X
Retry analysesXX
See analysis logsXXX
See repository settingsXX
Enable inline commentsXX
Sync repositories with GitHubXX
Generate an SSH private keyX
Download an SSH public keyX
Delete an SSH private keyX
Add Slack integrationXX
Edit Slack integrationXX
Delete Slack integrationXX
Enable test modeXX
Edit analysis toolsXX
Restrict who can close issuesX

³ You must have Member or Owner permission to your organization.

⁴ It is possible to restrict closing issues. See Restricting access to Close button.

← Working with IssuesSkip Analyzing →
  • Permissions requirement for an organization
  • Permissions requirement for a repository
Sider Documentation
Docs
Getting StartedAnalysis ToolsEnterprise
Sider
Sider TopTerms of ServicePrivacy
Social
BlogGitHubStar
Copyright © 2019 Sider, Inc.