@elitedcs/ghl-mcp 3.90.0 → 3.91.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +30 -0
- package/README.md +1 -1
- package/dist/index.js +2844 -1033
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,35 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 3.91.0: The board and the brief open much faster
|
|
4
|
+
|
|
5
|
+
This release is everything in 3.90.1, plus the change below.
|
|
6
|
+
|
|
7
|
+
**The board and the brief open from the last read of each account, then refresh in the background.** The cockpit keeps what it last read from each client's GoHighLevel account and draws from it at once, while it reads GoHighLevel again behind the scenes. The board's status line says how old that read is, for example "Loaded 4 minutes ago".
|
|
8
|
+
|
|
9
|
+
**Before any change to an account, GHL Command checks it again.** The saved read is only for what you see on screen.
|
|
10
|
+
|
|
11
|
+
**Measured on one agency's board:** the board draws in about 0.3 seconds instead of 3.2, and the brief takes about 2.4 seconds instead of 7.5. Opening a client and switching between clients take the same time as before.
|
|
12
|
+
|
|
13
|
+
**Known limits.** The first time the board opens after you install, or after you change a key or your plan, its status line says "Loading from GoHighLevel…" while it reads every account, about 15 to 20 seconds for 32 accounts. Rarely, an Approve or a Run is refused with "could not reach" when another client's saved read is cleared at the same moment; nothing is changed, so press it again. Right after you save an intake, the board can show the answers from before the save for up to 15 minutes, while every action reads the account live.
|
|
14
|
+
|
|
15
|
+
## 3.90.1: Add them for me and Confirm and build add exactly the people you were shown
|
|
16
|
+
|
|
17
|
+
This release is everything in 3.90.0, plus the fix below. It fixes behavior that shipped in 3.89.0 and 3.90.0.
|
|
18
|
+
|
|
19
|
+
**Add them for me and Confirm and build now add exactly the people shown, mark anyone getting an admin login, and refuse if the team changed.** Step 7, Staff, lists each person with their job, marks anyone whose login will be an admin with "Admin login", and says where the list came from. Confirm and build names each login it will make, the same way, before anything is made. When you press, the cockpit reads the team again first. If it changed since you looked, nobody is added and the list is shown as it is now.
|
|
20
|
+
|
|
21
|
+
**One team, the same everywhere.** The team is Your team in step 5 when it has anyone on it, otherwise the client's intake. Your own intake draft counts only when the client has not submitted the intake. In 3.89.0 and 3.90.0 an older draft could add someone who had left, with an admin login, and Build could make logins from the intake while step 7 checked Your team.
|
|
22
|
+
|
|
23
|
+
**Someone already in the account keeps their login as it is.** If the list would give them a different level, step 7 says so, and you change it in GoHighLevel.
|
|
24
|
+
|
|
25
|
+
**After Add them for me, step 7 says what happened:** who was added, who already had a login, and anyone who got a login but is no longer on the team, so you can remove it in GoHighLevel.
|
|
26
|
+
|
|
27
|
+
**A new login is never made twice while GoHighLevel catches up.** GoHighLevel can take a minute to list a login it has just made. Until it does, step 7 and the board say the person "is still being set up in GoHighLevel", and Add them for me does not send them again, from any page or window, for up to 10 minutes. If GoHighLevel insisted on a password, step 7 now shows the one-time password, as the board does.
|
|
28
|
+
|
|
29
|
+
**Known limits, fixed in the next release.** The board's staff panel does not show when someone's login level differs from the list. If someone is taken off the team while their login is being made and the connection drops, step 7 can still say they could not be added. Without an agency key, step 7 says your plan does not let you add people. The staff step says Intake waits for it (only Build does), and says calendars and lead alerts will use the people found, which it does not check. Blueprint Review says staff are not in the account when it could not read them. When nobody's job says owner, Build makes the first person listed an admin, while Add them for me makes them a user; Build's confirmation shows it before anything is made.
|
|
30
|
+
|
|
31
|
+
After Add them for me or Confirm and build, check the client's GoHighLevel Users list.
|
|
32
|
+
|
|
3
33
|
## 3.90.0: the cockpit never acts on the wrong client, and refuses a change made from an old page
|
|
4
34
|
|
|
5
35
|
This release is everything in 3.89.0, plus the changes below.
|
package/README.md
CHANGED