Profile Picture Upload

Your profile picture appears throughout GitScrum - in comments, task assignments, team lists, and your profile page. A recognizable photo helps team members identify you quickly.

Overview

Profile pictures are displayed in:

All display sizes are circular crops of your uploaded image.

Uploading a Picture

Access Upload

From your profile page:

1. Hover over your current avatar
2. Click the camera icon overlay
3. Modal opens with upload interface

Alternatively:

• Click "Upload Photo" button if visible
• Camera icon appears on avatar corner

Upload Methods

Method 1: Drag and Drop

1. Open the upload modal
2. Drag image file from your computer
3. Drop onto the upload area
4. Image processes automatically

Method 2: Click to Browse

1. Open the upload modal
2. Click "Browse" link in upload area
3. File picker opens
4. Select image file
5. Image processes automatically

Supported Formats

Image Requirements

Processing

After selecting an image:

1. Upload - Image transfers to server
2. Processing - Server optimizes image
3. Storage - Saved to your profile
4. Display - Updates across GitScrum
5. Modal closes - Automatically on success

Progress Indicator

The upload area shows:

• Upload progress bar
• Processing status
• Success/error message

Automatic Updates

After successful upload:

• Profile page updates immediately
• Other pages update on next load
• Team members see new picture immediately
• Previous picture is replaced (not archived)

Image Guidelines

Recommended Photos

Common Issues

Professional Tips

For professional environments:

• Use recent photo (current appearance)
• Business appropriate
• Consistent with other professional profiles
• Consider team expectations

For casual environments:

• Personality welcome
• Avatars/illustrations acceptable
• Keep identifiable

Default Avatar

If no picture uploaded, GitScrum displays:

┌─────────────┐
│             │
│      J      │  ← First initial of name
│             │
└─────────────┘
    Green background

Default Appearance

This default ensures all users have some avatar even without uploading.

Changing Picture

Replace Current Picture

1. Click camera icon on current avatar
2. Upload new image
3. Old image replaced automatically

No confirmation required - new image immediately replaces old.

Reverting to Default

Currently, you cannot revert to the default initial avatar. To remove a custom picture:

1. Upload a placeholder image
2. Or contact support for removal

Technical Details

Image Storage

URL Structure

Profile pictures are served via CDN:

https://cdn.gitscrum.com/avatars/[user-id]/[hash].jpg

URLs change when picture is updated, ensuring fresh images load.

Privacy

Visibility

Your profile picture is visible to:

• All members of your workspaces
• Anyone viewing shared content where you're mentioned
• Not indexed by search engines

Image Ownership

• You retain ownership of uploaded images
• GitScrum has license to display within platform
• Images not shared externally without content

Removal Requests

To permanently remove an image:

1. Upload replacement image
2. Or contact support for data deletion

Troubleshooting

Upload Fails

Image Doesn't Update

If new image doesn't appear:

1. Hard refresh browser (Ctrl+F5)
2. Clear cache for GitScrum domain
3. Check other pages for update
4. Wait a few minutes for CDN propagation

Image Looks Wrong

Frequently Asked Questions

Can I upload an animated GIF?

No, only static JPEG and PNG images are supported. GIFs would upload but only show first frame.

What happens to my old picture?

Old pictures are replaced and deleted. GitScrum does not maintain a history of previous avatars.

Can workspace admins change my picture?

No, only you can change your profile picture. Admins cannot modify member avatars.

Is there a picture requirement?

No, profile pictures are optional. The default initial avatar displays if none is uploaded.

Can I use the same picture across multiple accounts?

Yes, you can upload the same image to different GitScrum accounts. Each account stores its own copy.

Related Pages

• Profile - Main profile settings
• Work Experience - Career history
• Team Members - View team profiles

Email Preferences

Control which emails GitScrum sends to your inbox. Configure notification preferences to receive relevant updates without inbox overload.

Overview

Email preferences are located on your profile page in the sidebar. Each preference toggles a category of emails on or off. Changes save automatically when toggled.

Available Preferences

Offers & Promotions

When enabled, you'll receive:

• Subscription discount offers
• Holiday promotions
• Partner deals
• Feature bundle offers

When disabled:

• No promotional content sent
• Still receive essential account emails

Product Updates

When enabled, you'll receive:

• New feature announcements
• Major version updates
• UI/UX changes
• Integration additions
• Performance improvements

When disabled:

• No product news sent
• May miss important changes
• Critical updates still sent

Weekly Digest

When enabled, you'll receive weekly email with:

• Tasks completed this week
• Time logged summary
• Upcoming deadlines
• Project activity highlights
• Personal productivity metrics

When disabled:

• No weekly summary sent
• View metrics in app instead

Managing Preferences

Changing Settings

1. Navigate to your Profile
2. Locate Email Preferences in sidebar
3. Toggle any preference switch
4. Changes save automatically

Visual Feedback

No confirmation message appears - changes are instant.

Non-Configurable Emails

Certain emails cannot be disabled for security and operational reasons:

Security Notifications

Always sent:

• Password change confirmations
• New device sign-ins
• Two-factor authentication changes
• Suspicious activity alerts
• Account recovery emails

Account Emails

Always sent:

• Email verification
• Welcome email (first time only)
• Account deletion confirmation
• Terms of service updates

Billing Emails

Always sent:

• Invoice receipts
• Payment confirmations
• Payment failures
• Subscription changes
• Plan expiration warnings

Support Emails

Always sent:

• Support ticket responses
• Ticket status changes

Frequency

Product Updates

Weekly Digest

Promotions

Email Content

Weekly Digest Example

Your GitScrum Weekly Digest
Week of December 16-22, 2024

📊 Your Activity
- 12 tasks completed
- 38 hours logged
- 3 sprints updated

📅 Upcoming
- 4 tasks due this week
- Sprint "Q4 Release" ends Friday

🎯 Highlights
- Closed 95% of sprint commitments
- Focus score: 78 (healthy)

View full details in GitScrum →

Product Update Example

New in GitScrum: Time Tracking Reports

We've added powerful new reporting features:

✓ Export timesheets to PDF/CSV
✓ Filter by date range, project, member
✓ Billable vs non-billable breakdown
✓ Client-ready invoice support

Try it now →

Best Practices

Recommended Setup

For most users:

For Minimal Email

If you prefer fewer emails:

You'll still receive security and billing emails.

For Maximum Updates

If you want all communications:

Troubleshooting

Not Receiving Emails

If enabled preferences don't result in emails:

1. Check spam folder - GitScrum emails may be filtered
2. Verify email address - Ensure profile email is correct
3. Add to contacts - Whitelist @gitscrum.com
4. Wait for trigger - Some emails only send on specific events

Too Many Emails

If receiving unwanted emails:

1. Review preferences - Toggle off unnecessary categories
2. Check source - Ensure emails are actually from GitScrum
3. Contact support - Report if non-configurable emails seem excessive

Preferences Not Saving

If toggles don't persist:

1. Wait for update - Brief loading period
2. Refresh page - Verify current state
3. Check connection - Ensure internet connectivity
4. Try again - Toggle once more

Privacy

Data Usage

Email preferences data:

• Stored in your account profile
• Used only for email delivery decisions
• Not shared with third parties
• Not used for marketing targeting

Unsubscribe Links

All promotional emails include:

• One-click unsubscribe link
• Link to manage preferences
• No questions asked removal

Frequently Asked Questions

Can I change email address for notifications?

Notifications go to your account email. To change, update your profile email address. All notifications will then go to the new address.

Do preferences sync across workspaces?

Email preferences are account-level, not workspace-level. One set of preferences applies to all your workspace memberships.

Can workspace admins see my preferences?

No. Email preferences are private to your account. Admins cannot view or modify your settings.

Will I miss important updates if I turn off Product Updates?

Critical platform changes (downtime, security issues) are sent regardless of preferences. Feature announcements are opt-in.

How do I stop all emails?

You cannot stop security and billing emails. For everything else, toggle all preferences to Off. If you must receive zero emails, consider whether account deletion is appropriate.

Related Pages

• Profile - Main profile settings
• Support - Contact for email issues
• Billing - Billing email information

Profile Metrics

Profile Metrics provide data-driven insights into work patterns, capacity utilization, and contribution impact. These analytics help individuals understand their productivity and help managers support team sustainability.

Overview

Metrics are organized into four tabs on the profile page:

Health Tab

Monitor sustainability and prevent burnout through work pattern analysis.

Context Switching

Measures how often you switch between different projects, which research shows significantly impacts productivity.

Status Indicators:

• HEALTHY (green): Focus is maintained, manageable load
• MONITOR (yellow): Increasing context switches, attention needed
• CRITICAL (red): Heavy fragmentation, intervention recommended

Alert Example:

⚠ High context switching detected
Working on 6 projects simultaneously with 12 switches/day.
Estimated 25% productivity impact.

Load Distribution

Analyzes work intensity across time periods.

Status Interpretation:

• Consistent daily hours indicate sustainable pace
• High peak days may indicate crunch or poor estimation
• Excessive outside-hours work suggests overload
• Long periods without closure may indicate blocked work

Risk Indicators

Early warning signals for potential issues:

These indicators help identify when someone might be stuck, overwhelmed, or disengaged.

Work-Life Balance

Holistic view of sustainable work patterns:

Balance Score Calculation:

• Factors in regular hours, overtime, weekend work
• Adjusts for voluntary vs. required overtime
• Higher score = better balance

Capacity Tab

Understand time allocation and future availability.

Utilization Rate

How effectively available time is being used:

Why 70-85%?

• Under 70%: Potential underutilization
• 70-85%: Sustainable productivity
• Over 85%: No buffer for unexpected work

Weekly Utilization Chart: Visual bar chart showing utilization by week, making trends visible.

Availability Forecast

Future capacity for planning:

Example:

Next 2 weeks forecast:
Total: 80 hours
Committed: 50 hours
Buffer: 12 hours
Free: 18 hours

Project Distribution

Breakdown of time across projects:

Optimal Distribution:

• 1-2 anchor projects for deep focus
• 2-3 significant projects for variety
• Minimal scattered projects (overhead)

Warning: SCATTERED status indicates time fragmented across too many small projects.

Performance Tab

Track productivity trends over time.

Task Completion Velocity

Sprint Contribution

For teams using sprints:

Quality Indicators

Impact Tab

Measure contribution value beyond task counts.

Revenue Impact

For billable work:

Story Points Delivered

Aggregate effort contribution:

Contribution Categories

Understanding Status Colors

Consistent color coding across all metrics:

Who Can See Metrics

Metrics are private by default with access controlled by role.

Using Metrics Effectively

For Individuals

1. Monitor Health tab weekly for sustainability
2. Check Capacity before accepting new work
3. Track Performance trends, not daily fluctuations
4. Celebrate Impact achievements

For Managers

1. Review team Health to prevent burnout
2. Balance workloads using Capacity data
3. Support individuals showing warning signs
4. Recognize high-impact contributions

Common Patterns

Overload Pattern:

• High context switching
• Extended hours
• Weekend work
• Low engagement score

Underutilization Pattern:

• Low utilization rate
• High free capacity
• Few projects
• Low task velocity

Healthy Pattern:

• Focus on 1-2 projects
• Sustainable hours
• Consistent output
• Good work-life balance

Data Sources

Metrics are calculated from:

Accuracy depends on:

• Consistent time logging
• Task status updates
• Sprint planning completion
• Accurate effort estimates

Frequently Asked Questions

How often do metrics update?

Metrics refresh daily with overnight calculation. Real-time data may lag up to 24 hours.

Can I hide my metrics?

Metrics visibility is role-based. You cannot hide metrics from workspace administrators. You can always see your own metrics.

What if metrics seem wrong?

Verify:

• Time entries are logged correctly
• Task statuses are current
• Sprint assignments are accurate
• Check data within expected date range

Do metrics affect my standing?

Metrics are informational, not punitive. They exist to support sustainable work patterns and personal improvement, not performance management.

How far back does history go?

Metrics retain historical data for:

• 90 days detailed view
• 1 year summary view
• Longer retention for Pro workspaces

Related Pages

• Profile - Main profile page
• Time Tracking - Logging work hours
• Sprints - Sprint management

Two-Factor Authentication

Two-factor authentication (2FA) adds an extra layer of security to your GitScrum account. When enabled, you'll need both your password and a verification code from your authenticator app to sign in.

Why Enable 2FA

Account security matters. 2FA protects you against:

Even if someone obtains your password, they cannot access your account without the time-based code from your authenticator app.

Prerequisites

Before enabling 2FA, ensure you have:

1. Authenticator app installed on your mobile device:

• Google Authenticator (Android, iOS)
• Authy (Android, iOS, Desktop)
• 1Password (all platforms)
• Microsoft Authenticator (Android, iOS)
• Any TOTP-compatible app

1. Backup method ready to store recovery codes:

• Password manager
• Secure document
• Printed copy in safe location

Enabling 2FA

Step 1: Open 2FA Settings

1. Navigate to your Profile page
2. Click the 2FA button in the header (shows as "Enable 2FA" if not active)
3. Modal opens with setup instructions

Step 2: Scan QR Code

1. Open your authenticator app
2. Add account (usually + button)
3. Scan the QR code displayed in GitScrum
4. Account added to your authenticator

If you cannot scan the QR code:

• Click "Can't scan?" to reveal manual setup key
• Enter the key manually in your authenticator app

Step 3: Verify Setup

1. Enter the 6-digit code from your authenticator
2. Code changes every 30 seconds - use current code
3. Submit to verify

If verification fails:

• Ensure device time is correct (automatic time sync recommended)
• Wait for next code if current code is expiring
• Try rescanning QR code

Step 4: Save Recovery Codes

After successful verification:

1. Recovery codes display (10 single-use codes)
2. Copy codes using the Copy button
3. Store securely - password manager, secure document, or printed
4. Confirm you've saved codes
5. 2FA is now active

Recovery Codes:
ABC12-DEF34   GHI56-JKL78
MNO90-PQR12   STU34-VWX56
YZA78-BCD90   EFG12-HIJ34
KLM56-NOP78   QRS90-TUV12
WXY34-ZAB56   CDE78-FGH90

Important: Each recovery code works only once. Store them securely.

Signing In with 2FA

Once 2FA is enabled, the login process changes:

Normal Sign-In

1. Enter email and password as usual
2. Click Sign In
3. 2FA prompt appears
4. Open authenticator app
5. Enter current 6-digit code
6. Access granted

Using Recovery Code

If you cannot access your authenticator:

1. Enter email and password
2. Click "Use recovery code"
3. Enter one of your saved recovery codes
4. Access granted (that code is now invalidated)

Remember: Each recovery code works only once. Generate new codes if you've used several.

Managing 2FA

Viewing Current Status

Access 2FA settings from Profile:

• Green indicator: 2FA is enabled and active
• Message: "Your account is protected with two-factor authentication"

Viewing Recovery Codes

To see your current recovery codes:

1. Click 2FA management button
2. Select "View Recovery Codes"
3. Enter current 6-digit code to verify identity
4. Codes display - copy or note them

Regenerating Recovery Codes

If you've used recovery codes or suspect they're compromised:

1. Click 2FA management button
2. Select "Regenerate Codes"
3. Enter current 6-digit code to verify
4. New codes generated - old codes invalidated
5. Save new codes immediately

Warning: Regenerating codes invalidates ALL previous codes. Ensure you save the new set.

Disabling 2FA

To remove 2FA from your account:

1. Click 2FA management button
2. Select "Disable 2FA"
3. Warning displays about reduced security
4. Enter current 6-digit code to confirm
5. 2FA removed from account

Note: Disabling 2FA returns your account to password-only authentication. Consider the security implications before proceeding.

Recovery Scenarios

Lost Authenticator Access

If you lose your phone or cannot access your authenticator:

Option 1: Use Recovery Code

1. Select "Use recovery code" at login
2. Enter any unused recovery code
3. Sign in and immediately set up new authenticator

Option 2: Contact Support If you have no recovery codes:

1. Create support ticket from logged-out state
2. Provide account verification information
3. Support will assist with account recovery

Device Change

Moving authenticator to a new device:

Option 1: Multi-device apps (Authy)

• Authy syncs across devices automatically
• Install on new device and sign in to Authy account

Option 2: Manual migration

1. Before factory reset or losing old device:
2. Sign in to GitScrum
3. Disable 2FA
4. Set up new device with authenticator app
5. Re-enable 2FA (scan with new device)
6. Save new recovery codes

Time Sync Issues

If codes constantly fail:

Most authenticator apps have a time sync option in settings. Google Authenticator: Settings → Time correction for codes → Sync now.

Security Best Practices

Recovery Code Storage

Do:

• Store in password manager
• Keep encrypted backup
• Print and store in secure location
• Use secure notes app

Don't:

• Store in plain text files
• Email to yourself
• Take screenshots
• Share with others

Authenticator App Selection

Consider apps that support:

• Encrypted backups
• Multi-device sync
• Biometric protection
• Export/import functionality

Recommended:

• Authy - Cloud sync, multi-device
• 1Password - Integrated with password manager
• Google Authenticator - Simple, no account required

Account Protection

Complete security checklist:

1. ✓ Strong, unique password
2. ✓ 2FA enabled
3. ✓ Recovery codes stored securely
4. ✓ Email notifications for sign-ins enabled
5. ✓ Regular password updates

Frequently Asked Questions

What if I enter the wrong code?

You have multiple attempts before temporary lockout. Wait a moment and try the current code (codes change every 30 seconds).

Can I use SMS-based 2FA?

GitScrum uses TOTP (Time-based One-Time Password) via authenticator apps only. SMS is not supported due to security vulnerabilities.

Do I need 2FA for API access?

API tokens are separate from 2FA. Once you generate an API token, it works without 2FA verification. Protect API tokens as you would passwords.

Can workspace admins see my 2FA status?

Admins can see whether 2FA is enabled for workspace members but cannot access your codes, recovery codes, or disable your 2FA.

What happens to 2FA if I'm removed from workspace?

2FA is account-level, not workspace-level. It remains active regardless of workspace membership changes.

Troubleshooting

Code Not Working

1. Check time: Device clock must be accurate
2. Wait for new code: Don't use expiring codes
3. Verify account: Ensure scanning correct QR
4. Try recovery code: Use backup if needed

QR Code Won't Scan

1. Increase brightness: Ensure screen is visible
2. Clean camera: Remove obstructions
3. Use manual entry: Click "Can't scan?" option
4. Try different app: Some apps have better scanning

Locked Out

1. Use recovery code if available
2. Contact support if no recovery codes
3. Verify identity through support process
4. Regain access after verification

Related Pages

• Profile - Main profile settings
• Password Change - Update password
• Support - Contact support for account recovery

Password Change

Keep your GitScrum account secure by regularly updating your password. This guide covers how to change your password and what happens after.

Accessing Password Change

From your Profile page:

1. Navigate to Profile (click avatar → Profile)
2. Locate "Password" button in header section
3. Click to open password change modal

The button appears alongside the Edit Profile button, only visible when viewing your own profile.

Changing Your Password

Step 1: Open Modal

Click the Password button to open the change password dialog.

Step 2: Enter New Password

1. Type your new password in the field
2. Use the eye icon to toggle visibility
3. Verify you've typed correctly

Password Requirements

Step 3: Confirm Change

1. Click "Change" button
2. Wait for confirmation
3. Success message appears

After Password Change

Immediate Logout

After successful password change:

1. Confirmation displays: "Password changed!"
2. Countdown starts: "Logging out in 5s..."
3. Automatic redirect to login page
4. All sessions ended across all devices

Why Automatic Logout?

Security measure to ensure:

• Old sessions cannot continue using account
• Any compromised sessions are invalidated
• You must verify new password works
• Clean authentication state

Signing Back In

1. Enter your email
2. Enter new password
3. Complete 2FA if enabled
4. Access restored

Password Best Practices

Creating Strong Passwords

Do:

• Use 12+ characters when possible
• Mix uppercase, lowercase, numbers, symbols
• Use passphrases (multiple random words)
• Generate with password manager

Don't:

• Reuse passwords from other sites
• Use personal information (birthdays, names)
• Use sequential patterns (abc123, qwerty)
• Share passwords with others

Password Examples

Weak:
- password123
- john1985
- qwerty

Strong:
- Kx9#mP2$vL8nQ4@w
- correct-horse-battery-staple
- $unfl0wer!Mountain#2024

Update Frequency

Recommended password update schedule:

Password Recovery

Forgot Password

If you forget your password:

1. Go to login page
2. Click "Forgot password?"
3. Enter email address
4. Check email for reset link
5. Click link within 24 hours
6. Set new password

Reset Link Expiration

Password reset links expire after 24 hours for security. Request a new link if expired.

Troubleshooting

Password Not Accepted

If your new password is rejected:

Cannot Sign In After Change

1. Verify you're using the new password
2. Check caps lock is off
3. Clear browser autofill if outdated
4. Try "Forgot password" if unsure

Still Logged In Elsewhere

After password change, all sessions should end. If you notice activity:

1. Check active sessions in browser settings
2. Clear all browser cookies for GitScrum
3. Contact support if unauthorized access suspected

Security Notifications

When you change your password, GitScrum sends:

• Confirmation email about password change
• Alert if change was unexpected

If you receive notification about a password change you didn't make:

1. Immediately reset password
2. Enable 2FA if not active
3. Review account activity
4. Contact support if concerned

Related to Password

Two-Factor Authentication

Adding 2FA provides additional security beyond password:

• Password alone cannot access account
• Protects against password breaches
• Requires authenticator app code

See Two-Factor Authentication for setup.

Session Management

Your password protects all sessions:

• Browser sessions
• API token generation
• Mobile app access

Changing password ends all active sessions for security.

Frequently Asked Questions

Why am I logged out after changing password?

Security requirement. All sessions end to ensure any potentially compromised sessions are invalidated. This protects against unauthorized access if your old password was known by someone else.

Can I use my old password again?

Yes, GitScrum does not prevent password reuse. However, using a new unique password is recommended for security.

How long until I'm logged out?

A 5-second countdown displays after successful change. You're redirected to login after countdown completes.

What if I forget my new password immediately?

Use the "Forgot password" option on the login page to receive a reset link via email. Set a new password through that link.

Does password change affect API tokens?

No, existing API tokens remain valid after password change. Revoke tokens separately if needed.

Related Pages

• Profile - Main profile settings
• Two-Factor Authentication - Enhanced security
• Support - Account assistance

Work Experience

Document your professional journey on your GitScrum profile. Work experience entries showcase your expertise, build credibility with team members, and create a professional identity within your workspace.

Overview

The Work Experience section on your profile displays:

• Company and position history
• Employment dates
• Role descriptions
• Career timeline

Only profile owners can add, edit, or delete their work experience. All workspace members can view profile work experience.

Adding Work Experience

Access the Form

From your profile page:

1. Locate the Work Experience section
2. Click the add button (+) in the section header
3. Modal opens with experience form

Required Fields

Optional Fields

Completing the Form

Step 1: Company Information

Company: Acme Corporation
Position: Senior Software Engineer

Step 2: Employment Period

Start Date: January 2022
☐ I am currently working here
End Date: [leave blank if current]

Step 3: Description Write a brief summary of:

• Key responsibilities
• Notable achievements
• Technologies used
• Team size or scope

Step 4: Save Click "Add" to save the entry. Entry appears immediately on your profile.

Writing Effective Descriptions

What to Include

Description Examples

Good description:

Led backend development for payment processing platform serving 500K+ 
daily transactions. Architected microservices migration reducing latency 
by 40%. Mentored 3 junior developers. Stack: Node.js, PostgreSQL, Redis, 
Kubernetes.

Basic description:

Full-stack development for e-commerce platform. Built checkout flow 
and inventory management features. React, Python, AWS.

Keep It Concise

Profile descriptions should be scannable:

• 2-4 sentences maximum
• Bullet points work well
• Focus on impact, not tasks
• Quantify when possible

Current Position

Marking Current Job

For your current role:

1. Check "I am currently working here"
2. Leave End Date blank
3. Display shows "Present" instead of end date

Multiple Current Positions

You can have multiple current positions (contractor, consultant, multiple part-time roles):

• Mark each with "Currently working here"
• All display with "Present" as end date
• Sorted by start date

Editing Work Experience

Access Edit Mode

On any experience entry:

1. Hover over the entry
2. Click the pencil (edit) icon
3. Modal opens with current data

Making Changes

1. Modify any field as needed
2. Update dates if changed
3. Click "Save" to apply changes

What You Can Edit

Deleting Work Experience

Access Delete

On any experience entry:

1. Hover over the entry
2. Click the trash (delete) icon
3. Confirmation dialog appears

Confirming Deletion

Delete Work Experience

Are you sure you want to delete this work experience?

[Cancel]  [Delete]

Click "Delete" to permanently remove. This action cannot be undone.

Experience Display

Timeline View

Entries display chronologically:

[Company Logo]  Senior Software Engineer
                Acme Corporation
                Jan 2022 - Present

                Led backend development for payment processing platform...

[Company Logo]  Software Engineer
                Previous Corp
                Mar 2019 - Dec 2021

                Full-stack development for e-commerce platform...

Visual Elements

Empty State

Profile without experience shows:

For profile owner:

No Work Experience
Add your first experience to showcase your career.

For other viewers:

No work experience has been added yet.

Visibility

Who Can See

Privacy Notes

• Work experience is visible to all workspace members
• Cannot make individual entries private
• Consider what you share in descriptions
• Professional information only recommended

Best Practices

Complete Profile

A complete work history:

• Shows professional credibility
• Helps team understand your background
• Provides context for expertise

Keep Updated

Review and update when:

• Starting new position
• Changing roles at same company
• Leaving a position
• Achieving significant milestone

Professional Tone

Frequently Asked Questions

Can I reorder entries?

Entries automatically sort by start date (most recent first). Manual reordering is not available.

Is there a limit to entries?

No limit on work experience entries. Add as many positions as relevant.

Can I add non-work experience?

The work experience section is designed for employment history. Education, certifications, and projects are not currently supported.

Do entries sync anywhere?

Work experience is GitScrum-specific. It does not import from or export to LinkedIn or other platforms.

Can team members see my salary?

No. There is no salary field. Work experience only includes company, position, dates, and description.

What happens if I leave the workspace?

Your profile and work experience remain on your account. If you rejoin the workspace later, your data is preserved.

Related Pages

• Profile - Main profile settings
• Profile Picture Upload - Avatar management
• Team Members - View workspace members