---
schema_version: "1"
id: 7ba51eeaa96ea8e0a83970bbc9eae19635a85e01f9d36d0763738f7559864bb2
title: Are You Sharing a Development Environment?
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_dev_environment_sharing.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_dev_environment_sharing.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bea42be207ac0904c2a6a51a0699df2f6f1504eb34c57b2710f11f0e15a9c473
description: Changes are associated in Lifecycle Center with the development environment within a project. Therefore, we recommend that all developers have their own development environment. A single development environment can be connected to multiple work items.
products:
  - Salesforce Platform
release: "264"
---
# Are You Sharing a Development Environment?

Changes are associated in Lifecycle Center with the development environment within a project. Therefore, we recommend that all developers have their own development environment. A single development environment can be connected to multiple work items.

Here are some considerations if you are sharing a development environment.

When you pull changes, the changed components are displayed in the changes list, but no files have been retrieved out of the development environment yet. The file isn’t actually retrieved from the development environment until it’s committed.

After a component is committed, it no longer appears in the changes list for any work item that is connected to that development environment, until the component is changed again in the development environment.

If multiple developers are using one development environment (within the same project), actions by one developer can have ramifications on the other. For example:

- If two developers are changing the same component, after one developer commits the component, it no longer shows up in the other developer’s change list (until the component is changed again in the development environment and pulled again). This disconnect can result in not all the needed files being included in a work item’s commit and feature branch.
- If someone else changed the component since you pulled it, the committed file is included with those latest changes. Consequently, the file you’re committing could be different than what you expect.
- When you pull changes, you see all the files changed by anyone who is making changes in the development environment, since the files’ last commit.
- If multiple developers are making changes in a shared development environment, the Last Modified By column in the changes list indicates who made the last change. So if you’re using that field to identify changes you’ve made, you could miss some if someone else has modified it more recently than you.