Lukas Steger
11/06/2025, 11:40 AMkapa.ai
11/06/2025, 11:41 AMkapa.ai
11/06/2025, 11:41 AMyaml models: - name: my_model_name meta: owner: "<@USER_ID>" For example, if the user ID is DGN6MQ07L, you would configure it as: yaml meta: owner: "<@DGN6MQ07L>" This format (<@USER_ID>) is what [Slack's API documentation recommends](https://slack.com/archives/C02CTC89LAX/p1669647715732819) for mentioning users and ensures you're tagging the exact user you intend to. To find a user's Slack ID, you can use the Slack API method users_lookupByEmail. As mentioned in the [community discussion](https://slack.com/archives/C02CTC89LAX/p1669647715732819): python client.users_lookupByEmail(email=email)["user"]["id"] This approach is particularly important for Slack Enterprise customers or workspaces where multiple users might share the same email prefix but have different email domains, as the email prefix method (@jessica.jones) may not reliably distinguish between them.Lukas Steger
11/07/2025, 10:49 AMkapa.ai
11/07/2025, 10:49 AMkapa.ai
11/07/2025, 10:49 AMmeta: owner: @jane for a table, it tags the old, deactivated Jane account and not the new one." The user was able to resolve this by using the entire email address instead of the email prefix: yaml meta: owner: "jane@new_company_url.com" However, the knowledge sources do not explicitly mention whether Elementary has a built-in feature to automatically skip deactivated Slack accounts when using email prefixes. The workaround provided was to use the full email address to distinguish between the active and deactivated accounts. If you'd like Elementary to add functionality to automatically filter for only active Slack accounts, you could consider opening a feature request on their [GitHub repository](https://github.com/elementary-data/elementary/issues/new?assignees=&labels=Feature+Request+%F0%9F%92%A1%2C+Triage+%F0%9F%91%80&projects=&template=feature_request.md&title=), as suggested by the Elementary team in similar feature discussions.