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 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 the visual identity of your workspace within GitScrum Studio.
Workspace Logo
The workspace logo appears in project contexts and workspace identification areas. Upload a square image (recommended minimum 256x256 pixels) in PNG, JPG, or SVG format.
To upload a logo:
- Click the upload area or drag and drop an image file
- Wait for the upload to complete
- 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 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 might be affected
To delete a workspace:
- Scroll to the Danger Zone section
- Click the "Delete Workspace" button
- Enter the workspace name exactly as shown to confirm
- Click "Permanently Delete"
If you are the only workspace owner and have no other workspaces, you will be prompted to create a new workspace or handle account-level settings before deletion completes.
Pro Tips (Once You Are Comfortable)
- Time-saver: Keep workspace names short but descriptive. You will see them frequently in navigation and switching contexts.
- Did you know? The workspace logo can be different from your company logo. Some teams use project-specific imagery for quick visual identification.
- Common mistake: Deleting a workspace thinking data can be recovered. Always export important data before deletion.
- Power 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 lack permission, contact the workspace owner.
Workspace Identity Best Practices
Choosing the Right Name
Your workspace name is seen throughout GitScrum, so choose wisely:
| Scenario | Good Name | Avoid |
|---|---|---|
| Company | "Acme Corporation" | "AC" or "My Company" |
| Department | "Marketing Team" | "Team" or "Department" |
| Client work | "Client XYZ Projects" | "Client1" |
| Product | "Mobile App Development" | "App" |
When to Use Multiple Workspaces
Consider separate workspaces for:
- Different clients (for confidentiality and billing separation)
- Distinct departments (when teams don't overlap)
- Separate products (when release cycles differ significantly)
- Testing/sandbox (for training new team members)
Keep related work in a single workspace when:
- Teams frequently collaborate
- Resources are shared across projects
- Unified reporting is needed
- Single billing structure applies
Branding Guidelines
Logo Specifications
For optimal display across GitScrum:
| Element | Recommended Size | Format | Notes |
|---|---|---|---|
| Workspace Logo | 256x256px | PNG, SVG | Square, transparent background |
| Favicon | 32x32px or 64x64px | ICO, PNG | Simple, recognizable |
Logo Design Tips
- Use simple designs that scale well
- Ensure sufficient contrast with dark backgrounds
- Test visibility at small sizes
- Consider using icon-only version of logo
- Maintain consistent branding across workspaces
Description Content Strategies
For Client Workspaces
Include:
- Client contact information
- Contract or project reference numbers
- Key stakeholders and their roles
- Links to client documentation
- Communication preferences
For Internal Teams
Include:
- Team mission or objectives
- Key resources and documentation links
- On-call or escalation contacts
- Meeting schedule links
- Team communication channels
Template Example
Team: [Team Name]
Lead: [Name] (@username)
Slack: #channel-name
Wiki: [link]
Goals: [Current quarter objectives]Workspace Lifecycle Management
Before Deleting a Workspace
Complete this checklist:
- Export time tracking data for billing records
- Download documents from project document sections
- Export wiki content if documentation is valuable
- Notify all team members of impending deletion
- Archive projects individually if selective retention needed
- Cancel any active subscriptions tied to the workspace
- Verify no critical client data will be lost
Archiving vs Deleting
If you're unsure about deletion:
| Use Archive When | Use Delete When |
|---|---|
| May need data later | Data is obsolete |
| Regulatory retention required | No compliance requirements |
| Historical reference valuable | Clean slate preferred |
| Temporary pause | Permanent end |
Archived projects remain accessible but hidden from active views.
Troubleshooting General Settings
Logo Not Displaying
If your uploaded logo doesn't appear:
- Check file format (PNG, JPG, SVG supported)
- Verify file size (under 5MB recommended)
- Clear browser cache (Ctrl+Shift+R)
- Try a different browser
- Ensure image dimensions are reasonable (not excessively large)
Cannot Delete Workspace
If the delete button is disabled or fails:
- Verify you are the Agency Owner
- Check that all projects have been reviewed
- Ensure no active billing subscriptions block deletion
- Contact support if the issue persists
Name Change Not Reflected
If workspace name changes don't appear everywhere:
- Refresh the page (F5 or Ctrl+R)
- Clear browser cache
- Log out and log back in
- Note that URL slugs don't change with name changes
How to Report a Problem or Request a Feature
If you encounter issues with general settings or have suggestions, submit feedback through GitScrum Studio. In the Sidebar, click on Support Tickets and open a ticket describing your request.
Related Documentation
- Workspace Settings Overview - All workspace settings
- Work Schedule Settings - Configure work hours
- Invoice Settings - Billing configuration
- Team Members - Managing workspace access