You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All development work in Adobe Developer Console is done as part of a project. The concept of a project corresponds to an application you are building. To use APIs and services in the application, you can simply add those APIs and services to the Project. The project may include one or multiple products, and a combination of APIs, events, runtime, and plugins.
3
+
All development work in Adobe Developer Console is done as part of a Project. The concept of a Project corresponds to an application you are building. To use any APIs and services in your application, you must add them to the Project. The Project may include one or multiple products, and a combination of APIs, I/O Events, I/O Runtime, and Plugins.
4
+
5
+
+[Projects Overview](#projects-overview)
6
+
+[Projects in an enterprise organization vs personal developer organization](#projects-in-an-enterprise-organization-vs-personal-developer-organization)
7
+
+[View all Projects](#view-all-projects)
8
+
+[Export all Projects details](#export-all-projects-details)
+[View and manage a Project](#view-and-manage-a-project)
15
+
+[View a Project's Activity Log](#view-a-projects-activity-log)
16
+
+[Last service activity in a Project](#last-service-activity-in-a-project)
17
+
+[Project approval](#project-approval)
18
+
+[Beta users](#beta-users)
19
+
+[Delete a Project](#delete-a-project)
20
+
+[Find deleted Projects](#find-deleted-projects)
21
+
4
22
5
23
## Projects in an enterprise organization vs personal developer organization
6
24
7
-
Projects are a common framework within enterprise and personal developer organizations. Projects created under an enterprise organization are owned by the organization and are visible to other organization members. In contrast, projects belonging to a developer organization are visible only to you.
25
+
Projects are a common framework within enterprise and personal developer organizations. Projects created under an enterprise organization are owned by the organization and are visible to other organization members. In contrast, Projects belonging to a developer organization are visible only to you.
8
26
9
-
If you are a developer or a system administrator on multiple organizations, you can view the projects that are owned by those organizations. The projects you see on the Developer Console depends on the organization you have currently selected in the [org switcher](../getting-started.md#switching-between-your-organizations). Use the org switcher to view the organizations to which you belong to and easily switch between them.
27
+
If you are a developer or a system administrator on multiple organizations, you can view the Projects that are owned by those organizations. The Projects you see on the Developer Console depends on the organization you have currently selected in the [org switcher](../getting-started.md#switching-between-your-organizations). Use the org switcher to view the organizations to which you belong to and easily switch between them.
10
28
11
29
<InlineAlertslots="text"/>
12
30
13
-
**Note:** To create projects for enterprise organizations, you must have a system administrator or developer role. For information on managing developers in the admin console, see the documentation on [managing developers](https://helpx.adobe.com/enterprise/using/manage-developers.html).
14
-
15
-
## Create a New Project
31
+
To create Projects for enterprise organizations, you must have a system administrator or developer role. For information on managing developers in the admin console, see the documentation on [managing developers](https://helpx.adobe.com/enterprise/using/manage-developers.html).
16
32
17
-
### Empty Projects
18
33
19
-
Think of an empty project as an open canvas or "blank slate" into which you can add events, runtime, plugins, APIs, and more to create custom applications.
34
+
## View all Projects
20
35
21
-
To get started, follow the steps provided in the guide for [creating an empty project](projects-empty.md).
36
+
The [list of Projects](https://developer.adobe.com/console/projects/) page provides an overview of your organization's Projects. If you are part of an enterprise organization, the list of Projects will include all Projects in the organization (and not just the ones you created).
22
37
23
-
### Templated Projects
24
-
25
-
To streamline the creation of projects, Adobe Developer Console provides templates that you can use to get started quickly.
**Note:** Templated projects are currently only available for enterprise organizations.
40
+
On the page, you can view the Projects as cards or rows in a table. You can view the following details about a Project at a glance here
41
+
+ Project title
42
+
+ Services and workspaces added to the Project
43
+
+ Who last modified the Project and when
44
+
+ Project's last service activity
45
+
+ If the Project requires your attention
46
+
+ If the Project is Read-only or Auto-Generated
28
47
29
-
To get started, follow the steps provided in the guide for [creating a templated project](projects-template.md).
48
+
Furthermore, you can sort the Projects based on created date, last modified date, and last service activity date. Sorting the Projects by last service activity will show your active Projects first.
The **Projects** screen provides an overview of your organization's projects. Suppose you are part of an enterprise organization. In that case, this includes all projects that you have access to and not just projects that you have created.
52
+
### Filter Projects
34
53
35
-
On the Projects screen, each project is shown as a card. A project card mentions the title of the project, its last modified date, and the number of workspaces it has, where applicable.
54
+
You can filter down the list of Projects to find your Projects quickly. You can filter the list of Projects using the following filters:
1. By Text: You can filter Projects by ID, title, description, workspace, IMS client ID, technical account ID, event registration id, plugin id, or Runtime namespace.
57
+
2. By who created or modified the Project
58
+
3. By what a Project Contains (APIs, Event Providers, and Plugins)
59
+
4. By whether a Project requires your attention
38
60
39
-
You can use the sort functionality to change the order in which projects are displayed or select the list view to see your projects in a list rather than shown as cards.
All the details available on the list of Projects page can be exported as a CSV file. To do so,
65
+
1. Go to the list of Projects page
66
+
2. Click the Actions overflow menu (three dots) and select Export CSV
43
67
44
-
You can also begin working on a new project from the Projects screen by selecting **Create New Project**.
68
+
45
69
46
-
### Read Only view
70
+
### Read Only Projects
47
71
48
-
As a member of an enterprise organization, you may not have access to all of the services licensed by your organization. For this reason, you may see a *Read Only* tag on certain projects or workspaces within a templated project.
72
+
As a member of an enterprise organization, you may not have access to all of the services licensed by your organization. For this reason, you may see a *Read Only* tag on certain Projects or workspaces within a templated Project.
49
73
50
74
Although, Projects or workspaces marked as *Read Only* are still visible to you, but certain actions, such as downloading, editing, copying client secrets, or initiating the approval workflow, will be greyed out and inaccessible.
51
75
52
76
If you believe you are seeing a *Read Only* tag in error, or want access to certain services and product profiles, please work with your organization's administrators for access.
53
77
54
-
## Delete a Project
55
-
56
-
Deleting a project is **permanent** and will remove all entites contained within the project - APIs and services, credentials, and workspaces. You can delete a project by visiting the project overview page.
78
+
### Auto-Generated Projects
57
79
58
-
While most projects can be deleted, sometimes a project is related to an application you have published and, therefore, cannot be deleted.
80
+
Sometimes Adobe products automatically create Projects in your organization so you don't have to. In such cases, the Projects are marked Auto-Generated Projects.
59
81
60
-
1. If a project contains an API that was submitted for approval (status: In Review or Approved), then the project cannot be deleted.
61
-
2. If an App Builder project has been submitted for approval (status: Pending or Published), then that project cannot be deleted. However, you can always revoke a published app and then delete the project.
82
+
These Projects are shown to you for transparency, but cannot be modified or deleted by any user in the organization (even the system administrator). The Adobe product that created the Project automatically manages the Project and owns its lifecycle.
62
83
63
84
<InlineAlertslots="text"/>
64
85
65
-
Projects containing plugins cannot be deleted yet.
86
+
Auto-generated Projects containing Service Account (JWT) credentials will be migrated by Adobe and customers don't have to migrate such Projects.
87
+
88
+
89
+
## Create a New Project
90
+
91
+
### Empty Projects
92
+
93
+
Think of an empty Project as an open canvas or "blank slate" into which you can add events, runtime, plugins, APIs, and more to create custom applications.
94
+
95
+
To get started, follow the steps provided in the guide for [creating an empty Project](projects-empty.md).
96
+
97
+
### Templated Projects
98
+
99
+
To streamline the creation of Projects, Adobe Developer Console provides templates that you can use to get started quickly.
100
+
101
+
**Note:** Templated Projects are currently only available for enterprise organizations.
102
+
103
+
To get started, follow the steps provided in the guide for [creating a templated Project](projects-template.md).
104
+
66
105
67
-
## View a Project's Activity Log
106
+
## View and manage a Project
68
107
69
-
Any user in your organization who has access to the Developer Console and has access to the set of product profiles used in a project can view, edit, and delete that project.
108
+
Once you select a Project on the list of Projects page, you will land on the Project overview page. This page shows you details about the Project.
70
109
71
-
However, all modifications to a project on the Developer Console are captured in the project's activity log. The activity log serves as a record of "who did what and when?", enabling an organization to track changes made to a project.
110
+
+ Project title and description
111
+
+ Services and workspaces added to the Project
112
+
+ Who last modified the Project and when
113
+
+ Who created the Project and when
114
+
+ Project's last service activity
115
+
+ Email alerts status
116
+
+ If the Project requires your attention
117
+
+ If the Project is Read-only or Auto-Generated
72
118
73
-
Changes made to a project are retained as activity logs for **1 year**. You can also export the activity log records as a CSV file, if you wish to store them for longer.
119
+
On the left nav, you can access more information about the Project.
120
+
+ The insights page shows API and service activity recorded by Adobe.
121
+
+ The activity log page contains a log of modifications done to the Project.
122
+
+ The credential overview, API overview, event registration overview, Runtime overview, and workspace overview pages.
123
+
+ And, the Project Approval and Beta users pages, when applicable.
124
+
125
+
126
+
### View a Project's Activity Log
127
+
128
+
Any user in your organization who has access to the Developer Console and has access to the set of product profiles used in a Project can view, edit, and delete that Project.
129
+
130
+
However, all modifications to a Project on the Developer Console are captured in the Project's activity log. The activity log serves as a record of "who did what and when?", enabling an organization to track changes made to a Project.
131
+
132
+
Changes made to a Project are retained as activity logs for **1 year**. You can also export the activity log records as a CSV file, if you wish to store them for longer.
Note: Project Activity logs are currently only available to enterprise and teams organizations.
138
+
Note: Activity logs are currently unavailable in personal developer organizations.
139
+
80
140
81
-
## Last service activity in a Project
141
+
###Last service activity in a Project
82
142
83
143
At a glance, the last service activity date informs you when Adobe last recorded activity from your integration or application. This information helps ascertain whether the integration or application using this Project has been active.
84
144
@@ -93,21 +153,50 @@ Currently, we do not yet track service activity when
93
153
94
154
<InlineAlertslots="text"/>
95
155
96
-
The Developer Console only records the date of the service activity. Furthermore, the tracked information is approximate and only serves to inform you about which of your projects were in use and when. Historical data for service activity before April 15, 2024 is unavailable.
156
+
The Developer Console only records the date of the service activity. Furthermore, the tracked information is approximate and only serves to inform you about which of your Projects were in use and when. Historical data for service activity before April 15, 2024 is unavailable.
157
+
97
158
98
-
## Project approval
159
+
###Project approval
99
160
100
-
Once you have completed development on your project, your application is ready for approval. There are four different approval processes within Adobe Developer Console, depending on the type of application that you have built.
161
+
Once you have completed development on your Project and your application is ready for approval. There are four different approval processes within Adobe Developer Console, depending on the type of application that you have built.
101
162
102
163
1. Self-service push to production for OAuth credential
103
164
2. Approval process for OAuth credentials
104
165
3. Approval process for App Builder applications
105
-
4. Review process to publish plugins
106
166
107
-
To read more about the approval process, visit the [project approvals](approval.md) documentation.
167
+
To read more about the approval process, visit the [Project approvals](approval.md) documentation.
168
+
169
+
170
+
### Beta users
171
+
172
+
When building a Project containing OAuth credentials, Console enables you to select and manage a group of beta users, giving them access to your integration while it is still `In Development`. To learn more, read the [beta users overview](beta-users.md).
173
+
174
+
175
+
## Delete a Project
108
176
109
-
## Beta users
177
+
Deleting a Project is **permanent** and will remove all entites contained within the Project - APIs and services, credentials, and workspaces. You can delete a Project by visiting the Project overview page.
178
+
179
+
While most Projects can be deleted, sometimes a Project is related to an application you have published and, therefore, cannot be deleted.
180
+
181
+
1. If a Project contains an API that was submitted for approval (status: In Review or Approved), then the Project cannot be deleted.
182
+
2. If an App Builder Project has been submitted for approval (status: Pending or Published), then that Project cannot be deleted. However, you can always revoke a published app and then delete the Project.
183
+
184
+
<InlineAlertslots="text"/>
185
+
186
+
Projects containing plugins cannot be deleted yet.
187
+
188
+
189
+
### Find deleted Projects
190
+
191
+
Once you delete a Project, you will be unable to access its Activity Log. However, you can view who deleted a Project and when on the Activity log shown on the [list of Projects](https://developer.adobe.com/console/projects/) page.
192
+
193
+
To navigate to the Projects Activity Log,
194
+
1. Go to the list of Projects page
195
+
2. Click the Actions overflow menu (three dots) and select Activity Log
196
+
197
+
<InlineAlertslots="text"/>
110
198
111
-
When building a project containing OAuth credentials, Console enables you to select and manage a group of beta users, giving them access to your integration while it is still `In Development`. To learn more, read the [beta users overview](beta-users.md).
199
+
Note: Activity logs are currently unavailable in personal developer organizations.
0 commit comments