Restricting access and edit permissions of metadata

A method, comprising:

• operating, by a computer system, a server-based application workspace;
• installing, by the computer system, application components for a particular application package into the server-based application workspace, wherein the particular application package specifies a plurality of application components;
• storing, by the computer system, first and second permission values for respective first and second application components of the plurality of application components that indicate that the first application component is accessible by other application packages and that the second application component is not accessible by other application packages;
• storing, by the computer system, subscription information indicating a user that is a developer for the particular application package, and one or more users, different from the developer, that are subscribers for the particular application package;
• storing, by the computer system, lock data for the particular application package that indicates permissions to edit individual ones of a plurality of application components for the particular application package, wherein the permissions for a given user are based upon whether the subscription information indicates that the given user is a developer or a subscriber;
• allowing a user identified as a subscriber to edit a particular application component;
• storing, by the computer system, edit information in a database indicating differences in the particular application component before and after the subscriber edits to the particular application component;
• detecting, by the computer system, a conflict between the subscriber edit and a developer edit to the particular application component;
• providing, by the computer system, the edit information and conflict details to the developer;
• and
• in response to the detecting, resolving, by the computer system, the conflict.

A non-transitory computer-readable medium having instructions stored thereon that are executable by a computer system to perform operations comprising:

• operating a server-based application workspace;
• identifying a user that is a developer for a particular application package, and a set of users that are subscribers for the particular application package;
• storing lock data for the particular application package, wherein the lock data indicates respective permissions for developers and subscribers that are different from the developer to edit at least a first and a second application component of a plurality of application components specified by the particular application package;
• and
• based on the lock data:
• permitting the developer to edit all of the application components of the particular application package;
• and
• denying requests from the subscribers to edit the first application component;
• and
• accepting requests from the subscribers to edit the second application component;
• storing edit information in a database indicating differences in the second application component before and after the subscriber edits;
• detecting, by the computer system, a conflict between a particular subscriber edit and a particular developer edit to the second application component;
• providing the edit information to the developer;
• and
• in response to the detecting, resolving the conflict.