General Settings

The General Settings tab contains core workspace configuration options including basic information, branding elements, and the danger zone for workspace deletion.

Basic Information

Workspace Name

The workspace name identifies your workspace throughout GitScrum Studio. It appears in the header, navigation, and workspace selection menus. Choose a name that clearly identifies your organization, team, or client.

The workspace name is required and must be unique within your account. Changing the workspace name does not affect the workspace URL slug, which remains constant after creation.

Description

The description field provides additional context about the workspace's purpose. While optional, a good description helps team members understand what projects and work belong in this workspace.

Consider including:

• Team or department name
• Primary client or product area
• Key contacts or resources
• Links to important documentation

The description appears in workspace listings and selection screens, helping users quickly identify the correct workspace when you have multiple workspaces.

Branding Section

Branding options customize your workspace's visual identity within GitScrum Studio.

Workspace Logo

The workspace logo appears in project contexts and workspace identification areas. Upload a square image (minimum recommended 256x256 pixels) in PNG, JPG, or SVG format.

To upload a logo:

1. Click the upload area or drag and drop an image file
2. Wait for upload to complete
3. The new logo appears immediately

To remove a logo, click the remove button next to the current logo.

Danger Zone

The danger zone contains irreversible actions that require careful consideration.

Delete Workspace

Deleting a workspace permanently removes:

• All projects within the workspace
• All tasks, sprints, user stories, and related data
• All time tracking entries and invoices
• All team member associations (members themselves are not deleted, just disconnected)

This action cannot be undone. Before deleting, consider:

• Exporting any data you need to retain
• Notifying team members who use this workspace
• Checking for active client projects that may be affected

To delete a workspace:

1. Navigate to the Danger Zone section
2. Click the "Delete Workspace" button
3. Enter the workspace name exactly as shown to confirm
4. Click "Delete Permanently"

If you are the sole owner of the workspace and have no other workspaces, you will be prompted to create a new workspace or handle account-level settings before deletion completes.

Pro Tips (When You're Comfortable)

• Saves time: Keep workspace names short but descriptive. You'll see them frequently in navigation and context switching.

• Did you know? The workspace logo can be different from your company logo. Some teams use project-specific images for quick visual identification.

• Common mistake: Deleting a workspace thinking data can be recovered. Always export important data before deleting.

• Advanced move: Use the description to create a mini-wiki with links to team resources, making onboarding smoother for new members.

Permissions

Only Agency Owners can access and modify General Settings. If you need to make changes but don't have permission, contact the workspace owner.

How to Report an Issue or Request a Feature

If you encounter issues with general settings or have suggestions, submit feedback through GitScrum Studio. In the Sidebar, click Support Tickets and open a ticket describing your request.

Invoice Settings

The Invoice Settings tab configures default financial parameters for invoices generated from your workspace. These settings pre-fill invoice fields and establish your billing identity.

Legal Information

Legal Name

Enter your business legal name as it should appear on invoices. This is typically your registered company name, not a trading name or brand. The legal name appears at the top of generated invoices and in formal business correspondence.

Legal Email

The legal email is the official contact address for billing inquiries. Clients will see this on invoices as the billing contact. Use a dedicated billing email if possible (like billing@yourcompany.com) rather than a personal address.

Tax Number

Enter your tax identification number (VAT number, EIN, or equivalent depending on your jurisdiction). This number appears on invoices for tax compliance and client record-keeping.

If your business is not registered for tax purposes or your jurisdiction doesn't require this, you can leave this field empty.

Invoice Prefix

The invoice prefix appears before invoice numbers, helping organize and identify invoices. Common patterns include:

• Company initials: "ABC-" produces invoices like "ABC-001"
• Year-based: "2026-" produces "2026-001"
• Client type: "PROJ-" for project work, "RET-" for retainer invoices

The prefix is optional. Without it, invoices use only sequential numbers.

Address Information

Address Line 1

Enter your primary business address. This is typically the street address.

Address Line 2

Use for additional address information like suite numbers, building names, or floor numbers. This field is optional.

City

Enter the city where your business is located.

Postal Code

Enter your postal or zip code.

These address fields appear on invoices as your business address and are used for legal and tax purposes. If you operate remotely without a physical address, use your registered business address.

Billing Rates

Currency

Select the default currency for your invoices. This determines:

• The currency symbol displayed on invoices
• How amounts are formatted
• What currency clients see when you send invoices

If you bill clients in different currencies, you can override this on individual invoices or at the client level. The workspace setting establishes the default.

Hourly Rate

Enter your default hourly billing rate. This rate is used when:

• Converting time entries into billable amounts
• Creating invoices from time log data
• Calculating project budgets in "hours x rate" mode

Individual team members and projects can have different rates that override this default. The workspace hourly rate serves as a fallback when no specific rate is defined.

Tax Rate

Enter your default tax percentage (such as VAT or sales tax). Enter the rate as a decimal value (for example, enter "23" for 23% tax, not "0.23").

The tax rate applies to invoice subtotals to calculate the total amount due. If you operate in a tax-exempt environment or handle taxes separately, set this to zero.

How Invoice Settings Apply

Invoice settings create defaults that flow through your invoicing workflow:

Invoice creation: When you create a new invoice, these values pre-fill the relevant fields. You can modify them per-invoice as needed.

Client defaults: Client records can have their own billing settings that override workspace defaults. This is useful when different clients have different tax requirements or preferred currencies.

Project budgets: Project budget settings can inherit the workspace hourly rate or define project-specific rates.

Time tracking: Billable time calculations use these rates to estimate invoice values before formally creating an invoice.

Pro Tips (When You're Comfortable)

• Saves time: Fill out all invoice settings during initial workspace setup. This prevents having to re-enter information on every invoice.

• Did you know? The invoice prefix can include dates. Using "2026-01-" for January invoices creates automatic monthly organization.

• Common mistake: Leaving the tax rate at zero when you should be charging tax. Double-check your local tax obligations before sending invoices.

• Advanced move: Set up different invoice prefixes for different invoice types (like "PROJ-" vs "MAINT-") and switch them when creating invoices to categorize your revenue.

Permissions

Only Agency Owners can modify Invoice Settings. These settings affect all invoices created in the workspace.

How to Report an Issue or Request a Feature

If you encounter issues with invoice settings or have suggestions for improvements, submit feedback through GitScrum Studio. In the Sidebar, click Support Tickets and open a ticket describing your request.

Work Schedule Settings

The Work Schedule tab configures default working hours and days for your entire workspace. These settings affect time tracking calculations, capacity planning, and availability indicators across all projects.

Work Days Configuration

The work days grid displays all seven days of the week. Click any day to toggle between working day or non-working day. Working days appear highlighted, while non-working days remain dimmed.

The default configuration includes Monday through Friday as working days. Many teams maintain this traditional schedule, but you can customize to match your organization's reality:

• Select Saturday and Sunday for teams with weekend schedules
• Deselect specific weekdays if your organization observes different rest days
• Create four-day work week configurations by deselecting one weekday

The counter below the grid shows how many work days per week you have configured. This number affects weekly capacity calculations throughout GitScrum Studio.

Hours Per Day

The hours per day slider sets the default working day length for your workspace. This value is used for:

• Converting between hours and days in time estimates
• Calculating weekly and monthly capacity
• Determining over-allocation warnings in workload views
• Time tracking reports and analytics

Most teams use 8 hours per day, matching a standard full-time schedule. Adjust this value if your organization uses different standard hours (for example, 7.5 hours or 6 hours for compressed schedules).

The interface shows weekly capacity based on your settings (hours per day multiplied by work days). This helps verify that settings match your expectations.

Holiday Management

The holidays section lets you define non-working days that fall on otherwise working days. Adding holidays ensures accurate capacity planning by excluding these dates from availability calculations.

Adding Holidays

To add a holiday:

1. Click "Add Holiday" to reveal the date picker
2. Select the holiday date
3. Click "Add" to save

Holidays display in chronological order. Each entry shows the formatted date with a remove button that appears on hover.

Holiday Considerations

When adding holidays:

• Add recurring holidays annually (the list doesn't auto-repeat year to year)
• Include company-specific holidays and observances
• Consider regional holidays if you have distributed teams
• Remember that individual team members may have additional personal time off not reflected here

How These Settings Apply

Work schedule settings establish workspace-level defaults. Here's how they interact with other parts of GitScrum Studio:

Project-level overrides: Individual projects can have their own work schedules that override workspace defaults. This is useful for projects with different requirements or client expectations.

Team member availability: Work schedules affect how available hours are calculated when viewing team workload or assigning tasks. A team member with 20 hours of tasks in a 40-hour week shows as 50% allocated.

Time tracking calculations: When converting time entries to reports, the system uses work schedule settings to determine working days in a period, expected hours, and utilization percentages.

Calendar views: Non-working days appear differently in calendar views, helping visualize when work is expected to happen.

Pro Tips (When You're Comfortable)

• Saves time: Add all known holidays for the year at once. This prevents capacity planning surprises later.

• Did you know? Hours per day affects burndown charts and velocity calculations. If your team consistently works fewer hours, adjusting this setting makes metrics more accurate.

• Common mistake: Forgetting to add regional holidays when working with international teams. Team members in different locations may have different holidays.

• Advanced move: Review and update work schedules quarterly to catch any changes in organizational policies or upcoming holiday schedules.

Permissions

Only Agency Owners can modify Work Schedule settings. These settings apply to the entire workspace, so changes affect all projects and team members.

How to Report an Issue or Request a Feature

If you encounter issues with work schedule settings or have suggestions for improvements, submit feedback through GitScrum Studio. In the Sidebar, click Support Tickets and open a ticket describing your request.