crowdtime-cli 0.17.0__tar.gz → 0.17.1__tar.gz

{crowdtime_cli-0.17.0 → crowdtime_cli-0.17.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: crowdtime-cli
-Version: 0.17.0
+Version: 0.17.1
 Summary: AI-powered time tracking CLI — a modern, developer-friendly alternative to Harvest
 Project-URL: Homepage, https://crowdtime.lat
 Project-URL: Documentation, https://crowdtime.lat/docs

{crowdtime_cli-0.17.0 → crowdtime_cli-0.17.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "crowdtime-cli"
-version = "0.17.0"
+version = "0.17.1"
 description = "AI-powered time tracking CLI — a modern, developer-friendly alternative to Harvest"
 readme = "README.md"
 license = {text = "Proprietary"}

{crowdtime_cli-0.17.0 → crowdtime_cli-0.17.1}/src/crowdtime_cli/__init__.py

@@ -1,3 +1,3 @@
 """CrowdTime CLI - AI-powered time tracking from the command line."""
 
-__version__ = "0.17.0"
+__version__ = "0.17.1"

{crowdtime_cli-0.17.0 → crowdtime_cli-0.17.1}/src/crowdtime_cli/skills/crowdtime/SKILL.md

@@ -99,7 +99,7 @@ Other log commands:
 ct log list --week                                  # This week's entries
 ct log list --task "Design" --billable              # Filter by task + billable
 ct log list --user <user-id>                        # See team member's entries (manager+)
-ct log list --format csv                            # CSV with financial columns
+ct log list --format csv                            # CSV (rate/amount columns are empty below manager)
 ct log edit <entry-id> --duration 3h               # Edit an entry
 ct log edit <entry-id> --task "Research"            # Change task
 ct log delete <entry-id>                           # Delete an entry
@@ -165,8 +165,8 @@ ct p -a                             # include archived
 #### Project Members
 ```bash
 ct projects assignable-users <project-id>            # Who can still be added (gives you the user IDs)
-ct projects update-member <project-id> <user-id> --role project_manager --rate 150  # Set per-project role & rate
-ct projects add-members <project-id> --user <uid1> --user <uid2> --role member --rate 120  # Bulk add
+ct projects update-member <project-id> <user-id> --role project_manager --rate 150  # Set per-project role & rate (--rate: manager+)
+ct projects add-members <project-id> --user <uid1> --user <uid2> --role member --rate 120  # Bulk add (--rate: manager+)
 ```
 
 **Adding someone to a project:** run `assignable-users` first to get the user
@@ -186,6 +186,8 @@ ct projects add-tasks <project-id> --task <tid1> --task <tid2>  # Bulk assign ta
 
 **Note:** `--client` on `projects create` accepts a client name. If the client doesn't exist yet, it will be auto-created.
 
+**Rates and money are manager+ only.** Hourly rates, budgets, fixed fees, billing types/modes, billable amounts, invoices and retainers are visible and editable only by account managers, admins and owners. For viewers, members and project managers the API returns these fields as `null`, silently ignores them on writes, and returns 403 on invoice/retainer endpoints. Don't offer rate or money operations to those roles, and never try to infer rates from other data.
+
 **Billing types** (*what* is charged): `time_and_materials` (default) or `fixed_fee` (an agreed price via `--fixed-fee`, billed instead of logged hours).
 
 **Billing modes** (*how* an hourly rate resolves, T&M only): `custom` (default), `per_task` (rate per task), `per_person` (rate per person).
@@ -567,5 +569,6 @@ Read `references/commands.md` for the full reference of every command, subcomman
 14. **Expenses** — when the user mentions expenses, receipts, or purchases, use the `ct expense` commands. Always suggest a category and ask if the expense is billable. If recording a billable expense for a client project, always set `--project` and `--billable` so it gets included automatically when the client is invoiced
 15. **Invoices include expenses** — when creating invoices with `ct invoice create --period`, billable expenses from the same period are automatically included as line items. Mention this to users so they know their expenses will appear on the invoice. Invoices can be grouped by `project`, `task`, `user`, `date`, or `none` via `--group-by`. Line items support discounts (`--discount-type fixed|percent|hours --discount-value N`)
 16. **Client contacts** — use `ct clients contacts` and `ct clients add-contact` to manage multiple contacts per client. Set `--primary` for the main point of contact. Use `--receives-invoices` to flag contacts who should receive invoice emails
-17. **Payroll** — payroll data is strictly confidential. Only HR managers, admins, and owners can access it. When the user asks about payroll, always use the `ct payroll` commands. Compensation types are `hourly` (rate × hours) or `salary` (fixed monthly). Rate changes are always effective from the 1st of a month. The payroll workflow is: configure compensation → run liquidation → approve → mark paid
-18. **PTO / Time Off** — always construct explicit `ct pto ...` commands. Never use magic routing or `ct ai parse` for PTO. Before requesting PTO, always confirm the exact date range with the user — date ambiguity is the most common source of mistakes. Use `YYYY-MM-DD` for a single day or `YYYY-MM-DD:YYYY-MM-DD` for a range. `ct pto request` creates a pending entry (the requester's approvers are notified by email); `ct pto add <user>` requires project manager+ with the subject in their scope, and creates an auto-approved entry. When reconciling missing hours for a user, always check `ct pto summary --user <email> --from X --to Y` before assuming the hours are missing. See `references/pto.md` for the full status lifecycle, kind definitions, and LLM guidance.
+17. **Rate confidentiality** — rates, budgets, amounts, invoices and retainers are manager+ only (see Projects). If a member, viewer or project manager asks about rates or billed amounts, tell them it's restricted to account managers instead of trying workarounds
+18. **Payroll** — payroll data is strictly confidential. Only HR managers, admins, and owners can access it. When the user asks about payroll, always use the `ct payroll` commands. Compensation types are `hourly` (rate × hours) or `salary` (fixed monthly). Rate changes are always effective from the 1st of a month. The payroll workflow is: configure compensation → run liquidation → approve → mark paid
+19. **PTO / Time Off** — always construct explicit `ct pto ...` commands. Never use magic routing or `ct ai parse` for PTO. Before requesting PTO, always confirm the exact date range with the user — date ambiguity is the most common source of mistakes. Use `YYYY-MM-DD` for a single day or `YYYY-MM-DD:YYYY-MM-DD` for a range. `ct pto request` creates a pending entry (the requester's approvers are notified by email); `ct pto add <user>` requires project manager+ with the subject in their scope, and creates an auto-approved entry. When reconciling missing hours for a user, always check `ct pto summary --user <email> --from X --to Y` before assuming the hours are missing. See `references/pto.md` for the full status lifecycle, kind definitions, and LLM guidance.

{crowdtime_cli-0.17.0 → crowdtime_cli-0.17.1}/src/crowdtime_cli/skills/crowdtime/references/commands.md

@@ -383,7 +383,7 @@ ct log list [options]
 | `--format` | string | Output: `table`, `json`, `csv` |
 | `--json` | flag | JSON output |
 
-CSV output includes financial columns: `hourly_rate`, `billable_amount`.
+CSV output includes financial columns: `hourly_rate`, `billable_amount`. They are empty for viewers, members and project managers (rates and amounts are manager+ only).
 
 Endpoint: `GET /time/`
 
@@ -969,6 +969,8 @@ ct projects create NAME [options]
 >
 > When the fee is billed, that project's hours in the period are linked to the fee line and marked invoiced, so they stop showing as outstanding work without ever being charged twice. Until then they stay uninvoiced and available.
 
+> **Confidentiality:** rates, budgets, fixed fees, billing settings, billable amounts, invoices and retainers are manager+ only. For viewers, members and project managers these fields come back `null`, are ignored on writes, and invoice/retainer endpoints return 403.
+
 **Billing modes** — *how* an hourly rate is resolved (T&M only):
 | Mode | Description |
 |------|-------------|
@@ -1064,7 +1066,7 @@ ct projects members PROJECT_ID [--json]
 | `PROJECT_ID` | string (required) | Project slug or UUID |
 | `--json` | flag | Output as JSON |
 
-Lists all members assigned to a project with their project role, org role, hourly rate, and user ID.
+Lists all members assigned to a project with their project role, org role, hourly rate, and user ID. Rates are `null` below manager.
 
 **Usage examples:**
 ```bash
@@ -1106,7 +1108,7 @@ ct projects update-member PROJECT_ID USER_ID [options]
 | `PROJECT_ID` | string (required) | Project slug or UUID |
 | `USER_ID` | string (required) | User UUID or email |
 | `--role` | string | Project-level role override (e.g. `project_manager`, `member`, `viewer`) |
-| `--rate` | float | Hourly rate override for this project member |
+| `--rate` | float | Hourly rate override for this project member (manager+; ignored for other roles) |
 | `--json` | flag | JSON output |
 
 Updates a member's project-specific role and/or rate. The `--role` sets a `project_role` that overrides the member's org-level role for this project only. Response includes `effective_role`, `org_role`, and `org_hourly_rate` for context.
@@ -1144,7 +1146,7 @@ ct projects add-members PROJECT_ID --user USER_ID [--user USER_ID ...] [--role R
 | `PROJECT_ID` | string (required) | Project slug or UUID |
 | `--user` | string (repeatable, required) | User UUID or email (specify multiple times) |
 | `--role` | string | Project role for all added members |
-| `--rate` | float | Hourly rate for all added members |
+| `--rate` | float | Hourly rate for all added members (manager+; ignored for other roles) |
 | `--json` | flag | JSON output |
 
 Bulk-adds multiple members to a project in a single operation.

{crowdtime_cli-0.17.0 → crowdtime_cli-0.17.1}/src/crowdtime_cli/skills/crowdtime/references/workflows.md

@@ -241,6 +241,8 @@ ct favorites start <id> -n "Sprint 42 planning"
 
 Set up a complete project with billing configuration, task presets, and team members in one go.
 
+> Rates, budgets and billing settings are manager+ only. For project managers and below, `--rate`, `--budget`, `--fixed-fee` and `--billing-mode` are ignored by the API — omit them.
+
 ```bash
 # 1. Create the project with a billing mode
 ct projects create "Website Redesign" --client "Acme Corp" --budget 200 --code WR -b --billing-mode per_person
@@ -264,7 +266,7 @@ ct projects switch website-redesign
 
 ### Configure Per-Person Billing
 
-When using `per_person` billing mode, each team member can have their own rate on the project.
+When using `per_person` billing mode, each team member can have their own rate on the project. Requires manager+.
 
 ```bash
 # Create project with per-person billing
@@ -406,7 +408,7 @@ ct org revoke-invite <invitation-id>
 # Change a member's role
 ct org update-member <user-id> --role project_manager
 
-# Update hourly rate
+# Update hourly rate (admin+; rates are never shown to members, viewers or project managers)
 ct org update-member <user-id> --rate 150
 
 # Update weekly capacity